search for: add_lib_enum_value

...gt; So you are suggesting that the backend take the opaque blob, peer through > it, map it to something else and then encode that? The llvm backend? No, it should probably be done by whatever produced the IR. If viewing this a part of the file format, having the FE create a metadata asking for (add_lib_enum_value, "foo.a") is not too different than than asking for a particular visibility or dll import. > This means that every > single new flag (also consider vendor extensions and non-GNU linkers) would > need their own mapping and would need additional support for every single > varia...

On Wed, Jan 3, 2018 at 4:13 PM, Rafael Avila de Espindola < rafael.espindola at gmail.com> wrote: > Saleem Abdulrasool via llvm-dev <llvm-dev at lists.llvm.org> writes: > > > 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 > >