We previously only parsed the first one.
Details
Details
- Reviewers
gkm thakis - Group Reviewers
Restricted Project - Commits
- rGeeac6b2becee: [lld-macho] Handle multiple LC_LINKER_OPTIONs
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
| lld/test/MachO/lc-linker-option.ll | ||
|---|---|---|
| 71 |
This line generates multiple LC_LINKER_OPTIONs. So the old test already had multiple, but since they were both -lSystem the issue wasn't noticed | |
| lld/test/MachO/lc-linker-option.ll | ||
|---|---|---|
| 71 | Well yes, but I mean how do you get clang (or some other compiler) to generate LLVM IR with this? Most people don't write LLVM IR by hand :) | |
| lld/test/MachO/lc-linker-option.ll | ||
|---|---|---|
| 71 | ah gotcha :) The cases I've been seeing are coming from Swift. It seems like Swift generates them even for simple programs: (base) ~/tmp: cat hello.swift
print("Hello, World!")
(base) ~/tmp: swiftc -c hello.swift
(base) ~/tmp: llvm-objdump --private-headers hello.o | grep LC_LINKER_OPTION
cmd LC_LINKER_OPTION
cmd LC_LINKER_OPTION
cmd LC_LINKER_OPTION | |
This line generates multiple LC_LINKER_OPTIONs. So the old test already had multiple, but since they were both -lSystem the issue wasn't noticed