tree 3cc18da9f80b9d4534af09fe82cbc65e6daac0bb
parent e03a2ef180013c861d9a9c0e473c7abc12c270e1
author Nico Weber <thakis@chromium.org> 1708087618 -0500
committer Copybara-Service <copybara-worker@google.com> 1708087804 -0800

[lld/MachO] Fix assert on unsorted data-in-code entries (#81758)

When the data-in-code entries are in separate sections, they are not
guaranteed to be sorted. In particular, 68b1cc36f3df marked some libc++
string functions as noinline, which leads to global ctors involving
strings now producing data-in-code sections in __TEXT,__StaticInit,
which is why this now happens in practice.

Since data-in-code entries are relatively rare and small, just sort
them. No observed performance impact.

See also crbug.com/41487860

GitOrigin-RevId: 624ea349d7fa3535760a21a05c9998c7978228a4