search for: extract_symbols

...is where how this is done is defined, and it looks like it does it by: * build LLVM.so * use nm+awk+sed to pick out the symbols starting with LLVM * build LLVM-C.so using a -reexport_library linker option I'm thinking that maybe we could make this not-darwin-specific by making use of utils/extract_symbols.py: * edit extract_symbols.py to add a --only_unmangled option (or maybe --only_prefix=LLVM or something like that) * on non-darwin use that instead of the existing command to get the symbols to export (or: make extract_symbols.py work on Darwin) * instead of building LLVM-C.so from LLVM.s...

...does it by: > > * build LLVM.so > > * use nm+awk+sed to pick out the symbols starting with LLVM > > * build LLVM-C.so using a -reexport_library linker option > > > > I'm thinking that maybe we could make this not-darwin-specific by making > > use of utils/extract_symbols.py: > > * edit extract_symbols.py to add a --only_unmangled option (or maybe > > --only_prefix=LLVM or something like that) > > * on non-darwin use that instead of the existing command to get the > > symbols to export (or: make extract_symbols.py work on Darwin) >...

...out the symbols starting with LLVM > >>> > * build LLVM-C.so using a -reexport_library linker option > >>> > > >>> > I'm thinking that maybe we could make this not-darwin-specific by > >>> > making > >>> > use of utils/extract_symbols.py: > >>> > * edit extract_symbols.py to add a --only_unmangled option (or maybe > >>> > --only_prefix=LLVM or something like that) > >>> > * on non-darwin use that instead of the existing command to get the > >>> > symbols to expo...

...* use nm+awk+sed to pick out the symbols starting with LLVM >>> > * build LLVM-C.so using a -reexport_library linker option >>> > >>> > I'm thinking that maybe we could make this not-darwin-specific by >>> > making >>> > use of utils/extract_symbols.py: >>> > * edit extract_symbols.py to add a --only_unmangled option (or maybe >>> > --only_prefix=LLVM or something like that) >>> > * on non-darwin use that instead of the existing command to get the >>> > symbols to export (or: make extract...

...rting with LLVM >> >>> > * build LLVM-C.so using a -reexport_library linker option >> >>> > >> >>> > I'm thinking that maybe we could make this not-darwin-specific by >> >>> > making >> >>> > use of utils/extract_symbols.py: >> >>> > * edit extract_symbols.py to add a --only_unmangled option (or >> maybe >> >>> > --only_prefix=LLVM or something like that) >> >>> > * on non-darwin use that instead of the existing command to get the >> >>&gt...

Hello list! So I'm wondering if there is a will to ship a DLL with the C API exported? LLVM currently ships with LTO.dll which has some C api functions exported, made from the export file tools/lto/lto.exports, so it would not be the first DLL LLVM shipped. Currently I (and the users of my project[1]) are building it ourselves using this script[2] derived from the LLVMSharp script[3]. Which

Hi folks, I've been working for a few months on a proposal to make it easier to develop out-of-tree passes, and have them linked either statically or dynamically, within LLVM. This includes automatic integration within clang, opt and bugpoint. The goal is to lower the bar for people who develop out-of tree passes: they can maintain their code base in a third-party repo, pick it at config