search for: lc_linkopt

...oes the linker ignore it? Well, if the linker doesn't support the feature, it would. In PE/COFF, it is encoded as a special section (.drectve). In fact, GNU ld doesn't have as complete of an implementation as lld/link and does ignore a bunch of options. MachO has a special load command (LC_LINKOPT) that encodes this. But, in both cases, it requires the linker to interpret it, and if it does not, then the same behavior would be observed. > I just find it very fishy to consider linker options as advisory. > Presumably if a user is passing them, then they are required for > correctn...

On Wed, Jan 3, 2018 at 4:02 PM, Saleem Abdulrasool <compnerd at compnerd.org> wrote: > Hello all, > > There was some interest from a number of a few people about adding support > for embedded linker options to ELF. This would be an extension that > requires linker support to actually work, but has significant prior art > with PE/COFF as well as MachO both having support

Hello all, There was some interest from a number of a few people about adding support for embedded linker options to ELF. This would be an extension that requires linker support to actually work, but has significant prior art with PE/COFF as well as MachO both having support for this. The desire here is to actually add support to LLVM to pass along the necessary information into the object