llvm-objdump.test has 3 array_pod_sort() used for symbolization.
array_pod_start() calls qsort() internally and can have different
behaviors across different libcs. Use llvm::stable_sort instead.
Details
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
LGTM. This is what I think is causing tools/llvm-objdump/X86/disassemble-functions.test to fail in some settings (see my comment https://reviews.llvm.org/D75631#1940245)
llvm/tools/llvm-objdump/llvm-objdump.cpp | ||
---|---|---|
1205–1208 | Also non allocatable sections have 0 for start address. Dunno if it's worth mentioning. |
llvm/tools/llvm-objdump/llvm-objdump.cpp | ||
---|---|---|
1205–1208 | Might be worth considering this as a future change. I think excluding sections that do not have SHF_ALLOC could cause issues in some cases where one might forget to set the appropriate section flags in assembly. |
llvm/tools/llvm-objdump/llvm-objdump.cpp | ||
---|---|---|
1207 | Here and below: stabalize -> stabilize. |
llvm/tools/llvm-objdump/llvm-objdump.cpp | ||
---|---|---|
1207 | Thanks! Fixed by 579a7a1938403c272706e91fe6c9367ff682eea1 |
Here and below: stabalize -> stabilize.