[PATCH] D40849: CodeGen: support an extension to pass linker options on ELF
Sean Silva via Phabricator via llvm-commits
llvm-commits at lists.llvm.org
Wed Dec 20 13:59:23 PST 2017
silvas added a comment.
It looks like this thread has evolved into a design discussion. It isn't clear to me that we all agree on what problem should be solved. Saleem, it seems like you have some interest in having the format be open-ended, while many others (myself included) seem to want this to be as locked-down as possible with a narrow set of really clearly defined operations. Saleem, could you maybe start an RFC on llvm-dev so we can have a higher-level design discussion? Off the top of my head, there are a couple things that have been mentioned in this thread but not really resolved:
- Should we discuss this with bfd and gold? If not, why not?
- I know the PlayStation proprietary linker has support for a similar feature (as James has been discussing) and IIRC there were private patches in the compiler for it. Is it in scope for this change to allow deleting those private patches from the PlayStation compiler?
- How does this interact with the similar functionality on COFF and MachO? Is it in scope to have a common IR representation for the three platforms?
- From my reading of the spec, SHT_NOTE is optional. But presumably information like extra library paths is actually semantically necessary for obtaining a correct link and must not be dropped. This also is related to the question of representing this as metadata in the IR.
More information about the llvm-commits