search for: irsymtab

Hi all, I've been making a number of changes to the summary representation recently, and I wanted to lay out some of my plans so that folks are aware of my ultimate direction with this. Basically I want to move the summary into the irsymtab that we will be storing to disk after D32061 lands. This would help solve a number of problems: - To read a summary, you need to read all summaries in a module. For example, if a client only wants to read summaries for prevailing symbols, it still needs to read summaries for all symbols. We should...

...>> Hi all, >> >> I've been making a number of changes to the summary representation >> recently, and I wanted to lay out some of my plans so that folks are aware >> of my ultimate direction with this. >> >> Basically I want to move the summary into the irsymtab that we will be >> storing to disk after D32061 lands. This would help solve a number of >> problems: >> - To read a summary, you need to read all summaries in a module. For >> example, if a client only wants to read summaries for prevailing symbols, >> it still needs...

...a comment(lib, "foo") would result in: > > > > .section ".autolink","eMS", at llvm_autolink,1 > > .asciz "foo" > > > > For LTO, equivalent information to the contents of a the .autolink > section will be written to the IRSymtab so that it is available to the > linker for symbol resolution. > > > > I'm not sure I understand the bit about "for symbol resolution". I > think that what you mean is that you will encode the autolink section > using symbols instead of as a section, and the linke...

..." pragmas map directly to. As an example, #pragma comment(lib, "foo") would result in: .section ".autolink","eMS", at llvm_autolink,1 .asciz "foo" For LTO, equivalent information to the contents of a the .autolink section will be written to the IRSymtab so that it is available to the linker for symbol resolution. The linker will process the .autolink strings in the following way: 1. Inputs from the .autolink sections of a relocatable object file are added when the linker decides to include that file (which could itself be in a library) in the li...

...>>> > >>> > .section ".autolink","eMS", at llvm_autolink,1 >>> > .asciz "foo" >>> > >>> > For LTO, equivalent information to the contents of a the .autolink >>> section will be written to the IRSymtab so that it is available to the >>> linker for symbol resolution. >>> > >>> >>> I'm not sure I understand the bit about "for symbol resolution". I >>> think that what you mean is that you will encode the autolink section >>> usin...

...> .section ".autolink","eMS", at llvm_autolink,1 >>>>> > .asciz "foo" >>>>> > >>>>> > For LTO, equivalent information to the contents of a the .autolink >>>>> section will be written to the IRSymtab so that it is available to the >>>>> linker for symbol resolution. >>>>> > >>>>> >>>>> I'm not sure I understand the bit about "for symbol resolution". I >>>>> think that what you mean is that you will encod...

...ma comment(lib, "foo") would result in: >> >> .section ".autolink","eMS", at llvm_autolink,1 >> .asciz "foo" >> >> For LTO, equivalent information to the contents of a the .autolink >> section will be written to the IRSymtab so that it is available to the >> linker for symbol resolution. >> >> The linker will process the .autolink strings in the following way: >> >> 1. Inputs from the .autolink sections of a relocatable object file are >> added when the linker decides to include that...

...using the explicit section attribute.   After discussions with Peter, I believe we don't need to introduce an   additional attribute. Step 2: Symbol resolution in the linker ======================================= The linker loads all bitcode input files and performs symbol resolution. The IRSymtab already exposes the explicit section attributes for symbols; in our case, all symbols now carry this information. (2.1) In addition to communicating the exisiting SymbolResolution flags (VisibileToRegularObj etc.), the linker also matches the linker script, determines an output section for each sy...

...ma comment(lib, "foo") would result in: >> >> .section ".autolink","eMS", at llvm_autolink,1 >> .asciz "foo" >> >> For LTO, equivalent information to the contents of a the .autolink >> section will be written to the IRSymtab so that it is available to the >> linker for symbol resolution. >> >> The linker will process the .autolink strings in the following way: >> >> 1. Inputs from the .autolink sections of a relocatable object file are >> added when the linker decides to include that...

...: >>>> >>>> .section ".autolink","eMS", at llvm_autolink,1 >>>> .asciz "foo" >>>> >>>> For LTO, equivalent information to the contents of a the .autolink >>>> section will be written to the IRSymtab so that it is available to the >>>> linker for symbol resolution. >>>> >>>> The linker will process the .autolink strings in the following way: >>>> >>>> 1. Inputs from the .autolink sections of a relocatable object file are >>>&g...

...gt; .section ".autolink","eMS", at llvm_autolink,1 >>>>>> .asciz "foo" >>>>>> >>>>>> For LTO, equivalent information to the contents of a the .autolink >>>>>> section will be written to the IRSymtab so that it is available to the >>>>>> linker for symbol resolution. >>>>>> >>>>>> The linker will process the .autolink strings in the following way: >>>>>> >>>>>> 1. Inputs from the .autolink sections of a re...

...t;,"eMS", at llvm_autolink,1 >>>>>>>> .asciz "foo" >>>>>>>> >>>>>>>> For LTO, equivalent information to the contents of a the .autolink >>>>>>>> section will be written to the IRSymtab so that it is available to the >>>>>>>> linker for symbol resolution. >>>>>>>> >>>>>>>> The linker will process the .autolink strings in the following way: >>>>>>>> >>>>>>>> 1. In...

...e. > After discussions with Peter, I believe we don't need to introduce an > additional attribute. > > Step 2: Symbol resolution in the linker > ======================================= > > The linker loads all bitcode input files and performs symbol resolution. The > IRSymtab already exposes the explicit section attributes for symbols; in our > case, all symbols now carry this information. > > (2.1) In addition to communicating the exisiting SymbolResolution flags > (VisibileToRegularObj etc.), the linker also matches the linker script, > determines an ou...

...t;,"eMS", at llvm_autolink,1 >>>>>>>> .asciz "foo" >>>>>>>> >>>>>>>> For LTO, equivalent information to the contents of a the .autolink >>>>>>>> section will be written to the IRSymtab so that it is available to the >>>>>>>> linker for symbol resolution. >>>>>>>> >>>>>>>> The linker will process the .autolink strings in the following way: >>>>>>>> >>>>>>>> 1. In...

...link,1 >>>>>>>>>> .asciz "foo" >>>>>>>>>> >>>>>>>>>> For LTO, equivalent information to the contents of a the >>>>>>>>>> .autolink section will be written to the IRSymtab so that it is available >>>>>>>>>> to the linker for symbol resolution. >>>>>>>>>> >>>>>>>>>> The linker will process the .autolink strings in the following >>>>>>>>>> way: >&g...

...gt;>>>>> .asciz "foo" >>>>>>>>>>>> >>>>>>>>>>>> For LTO, equivalent information to the contents of a the >>>>>>>>>>>> .autolink section will be written to the IRSymtab so that it is available >>>>>>>>>>>> to the linker for symbol resolution. >>>>>>>>>>>> >>>>>>>>>>>> The linker will process the .autolink strings in the following >>>>>>>...

Hi, Using master at b0a1c0b72c9c61f8b0a223e08f43498abb64f5e8, I cannot build LLVM. I configured with: CC=clang CXX=clang++ cmake -DCMAKE_INSTALL_PREFIX=$HOME/opt/llvm11-git \ -DCMAKE_BUILD_TYPE=Release \ -DLLVM_BUILD_LLVM_DYLIB=ON \ -DLLVM_LINK_LLVM_DYLIB=ON \ -DBUILD_SHARED_LIBS=OFF \ -DLLVM_ENABLE_EH=ON \ -DLLVM_ENABLE_RTTI=ON \