search for: sht_llvm_autolink

...;linker options" which, by nature, would tie source code to the vagaries of particular linkers. I don't see much value in supporting other linker operations so I suggest that the binary representation be a mergable string section (SHF_MERGE, SHF_STRINGS), called .autolink, with custom type SHT_LLVM_AUTOLINK (0x6fff4c04), and SHF_EXCLUDE set (to avoid the contents appearing in the output). The compiler can form this section by concatenating the arguments of the "comment lib" pragmas in the order they are encountered. Partial (-r, -Ur) links can be handled by concatenating .autolink sections w...

...; which, > by nature, would tie source code to the vagaries of particular linkers. I > don't see much value in supporting other linker operations so I suggest > that the binary representation be a mergable string section (SHF_MERGE, > SHF_STRINGS), called .autolink, with custom type SHT_LLVM_AUTOLINK > (0x6fff4c04), and SHF_EXCLUDE set (to avoid the contents appearing in the > output). The compiler can form this section by concatenating the arguments > of the "comment lib" pragmas in the order they are encountered. Partial > (-r, -Ur) links can be handled by concatenating...

...> nature, would tie source code to the vagaries of particular linkers. I >> don't see much value in supporting other linker operations so I suggest >> that the binary representation be a mergable string section (SHF_MERGE, >> SHF_STRINGS), called .autolink, with custom type SHT_LLVM_AUTOLINK >> (0x6fff4c04), and SHF_EXCLUDE set (to avoid the contents appearing in the >> output). The compiler can form this section by concatenating the arguments >> of the "comment lib" pragmas in the order they are encountered. Partial >> (-r, -Ur) links can be handled b...

...> nature, would tie source code to the vagaries of particular linkers. I >> don't see much value in supporting other linker operations so I suggest >> that the binary representation be a mergable string section (SHF_MERGE, >> SHF_STRINGS), called .autolink, with custom type SHT_LLVM_AUTOLINK >> (0x6fff4c04), and SHF_EXCLUDE set (to avoid the contents appearing in the >> output). The compiler can form this section by concatenating the arguments >> of the "comment lib" pragmas in the order they are encountered. Partial >> (-r, -Ur) links can be handled b...

...ource code to the vagaries of particular linkers. I >>>> don't see much value in supporting other linker operations so I suggest >>>> that the binary representation be a mergable string section (SHF_MERGE, >>>> SHF_STRINGS), called .autolink, with custom type SHT_LLVM_AUTOLINK >>>> (0x6fff4c04), and SHF_EXCLUDE set (to avoid the contents appearing in the >>>> output). The compiler can form this section by concatenating the arguments >>>> of the "comment lib" pragmas in the order they are encountered. Partial >>>>...

...es of particular linkers. I >>>>>> don't see much value in supporting other linker operations so I suggest >>>>>> that the binary representation be a mergable string section (SHF_MERGE, >>>>>> SHF_STRINGS), called .autolink, with custom type SHT_LLVM_AUTOLINK >>>>>> (0x6fff4c04), and SHF_EXCLUDE set (to avoid the contents appearing in the >>>>>> output). The compiler can form this section by concatenating the arguments >>>>>> of the "comment lib" pragmas in the order they are encountered. P...

...would tie source code to the vagaries of particular linkers. I >>> don't see much value in supporting other linker operations so I suggest >>> that the binary representation be a mergable string section (SHF_MERGE, >>> SHF_STRINGS), called .autolink, with custom type SHT_LLVM_AUTOLINK >>> (0x6fff4c04), and SHF_EXCLUDE set (to avoid the contents appearing in the >>> output). The compiler can form this section by concatenating the arguments >>> of the "comment lib" pragmas in the order they are encountered. Partial >>> (-r, -Ur) links...

.... I don't see much value in supporting other linker operations so I >>>>>>>> suggest that the binary representation be a mergable string section >>>>>>>> (SHF_MERGE, SHF_STRINGS), called .autolink, with custom type >>>>>>>> SHT_LLVM_AUTOLINK (0x6fff4c04), and SHF_EXCLUDE set (to avoid the contents >>>>>>>> appearing in the output). The compiler can form this section by >>>>>>>> concatenating the arguments of the "comment lib" pragmas in the order they >>>>>>&gt...

.... I don't see much value in supporting other linker operations so I >>>>>>>> suggest that the binary representation be a mergable string section >>>>>>>> (SHF_MERGE, SHF_STRINGS), called .autolink, with custom type >>>>>>>> SHT_LLVM_AUTOLINK (0x6fff4c04), and SHF_EXCLUDE set (to avoid the contents >>>>>>>> appearing in the output). The compiler can form this section by >>>>>>>> concatenating the arguments of the "comment lib" pragmas in the order they >>>>>>&gt...

...o the vagaries of particular linkers. I >>>>> don't see much value in supporting other linker operations so I suggest >>>>> that the binary representation be a mergable string section (SHF_MERGE, >>>>> SHF_STRINGS), called .autolink, with custom type SHT_LLVM_AUTOLINK >>>>> (0x6fff4c04), and SHF_EXCLUDE set (to avoid the contents appearing in the >>>>> output). The compiler can form this section by concatenating the arguments >>>>> of the "comment lib" pragmas in the order they are encountered. Partial >&...

...alue in supporting other linker operations so I >>>>>>>>>> suggest that the binary representation be a mergable string section >>>>>>>>>> (SHF_MERGE, SHF_STRINGS), called .autolink, with custom type >>>>>>>>>> SHT_LLVM_AUTOLINK (0x6fff4c04), and SHF_EXCLUDE set (to avoid the contents >>>>>>>>>> appearing in the output). The compiler can form this section by >>>>>>>>>> concatenating the arguments of the "comment lib" pragmas in the order they >>&gt...

...linker >>>>>>>>>>>> operations so I suggest that the binary representation be a mergable string >>>>>>>>>>>> section (SHF_MERGE, SHF_STRINGS), called .autolink, with custom type >>>>>>>>>>>> SHT_LLVM_AUTOLINK (0x6fff4c04), and SHF_EXCLUDE set (to avoid the contents >>>>>>>>>>>> appearing in the output). The compiler can form this section by >>>>>>>>>>>> concatenating the arguments of the "comment lib" pragmas in the order...