As @alexshap pointed out here,
it's a bit confusing to have the option to sort OutputSections with any
comparator when in practice we only use one.
Details
Details
- Reviewers
alexander-shaposhnikov gkm thakis - Group Reviewers
Restricted Project - Commits
- rG7599e98ab790: [lld-macho][nfc] Remove unnecessary parameterization of section sort
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
Once we handle N_COLD_FUNC this will also affect ordering. I don't know if that'd go in the one comparator or if it'd use a different comparator. If it's the latter, maybe we shouldn't change this?
Comment Actions
I think it'd use/extend the same comparator, since much of the ordering defined in the current comparator is needed for correctness.
lld/MachO/OutputSegment.cpp | ||
---|---|---|
98 | it's already wrapped at 80 :) |
lld/MachO/OutputSegment.cpp | ||
---|---|---|
65 | static auto compareByOrder(...) { return ... } |