search for: _llvm

...I am in a situation where I need to build x86 and arm assembly sources for some sources while the rest will be built with C. I do know that just adding `-fembed-bitcode` to a C sources would embed bitcode, but doing the same for the assembly files will not do that (at least, it will add the 1-byte `_LLVM,__asm` section, but not the `__LLVM,__bitcode` section). Furthermore, I do need the final output to contain bitcode for all files used. So, my question is if it is possible to add the `__LLVM,__bitcode` section later to the MachO object file. I tried to archive the bitcode using `xar` and run `llv...

Thanks for starting! Btw here is my CMD version: cmd /Q /V:ON /c "for /F "tokens=4" %l in ('dir llvm*.lib') do (for /F "tokens=2" %e in ('dumpbin /linkermember:1 %l ^| findstr "_LLVM"') do (set symbolname=%e & echo !symbolname:~1!))" You run it in the directory with all the llvm*.lib (yes the ThinLTO is excluded in this example but can be added easily i think) 2017-07-06 20:16 GMT+02:00 Jakob Bornecrantz <wallbraker at gmail.com>: > Made a bit of h...

...ny thanks! I was able to build a cross-compiler using your patch (with a minor change) and ran "hello world" in Qemu-ARM after compiling and linking it on x86_64. I put the list of outstanding bugs on a wiki page for tracking and reference: http://google2.osuosl.org/wiki/index.php/HowTo:_LLVM-based_cross_compiler I'll try to get the patch committed to llvm-gcc piece-meal. It looks like part of the patch includes the fix for http://llvm.org/PR2545 -- Chris said he's OK with the patch being committed, is there any reason it hasn't been applied yet? Does anyone mind if I do?...

...exander Benikowski <sebal007 at googlemail.com>: > Thanks for starting! > Btw here is my CMD version: > > cmd /Q /V:ON /c "for /F "tokens=4" %l in ('dir llvm*.lib') do (for /F > "tokens=2" %e in ('dumpbin /linkermember:1 %l ^| findstr "_LLVM"') do (set > symbolname=%e & echo !symbolname:~1!))" > > You run it in the directory with all the llvm*.lib (yes the ThinLTO is > excluded in this example but can be added easily i think) > > 2017-07-06 20:16 GMT+02:00 Jakob Bornecrantz <wallbraker at gmail.co...

...one and look for the recent one at >> home(if that didn't go down with my recent hdd crash): >> >> cmd /Q /V:ON /c "for /F "tokens=4" %l in ('dir llvm*.lib') do (for /F >> "tokens=2" %e in ('dumpbin /linkermember:1 %l ^| findstr "_LLVM"') do (set >> symbolname=%e & echo !symbolname:~1!))" >> >> What it does: >> >> For all *.lib files ina specific dir starting with LLVM call dumpbin.exe >> (tool from Visualstudio) and write all symbols with LLVM_ into a specific >> file &...

...for reference, i'll post this one and look for the recent one at home(if that didn't go down with my recent hdd crash): cmd /Q /V:ON /c "for /F "tokens=4" %l in ('dir llvm*.lib') do (for /F "tokens=2" %e in ('dumpbin /linkermember:1 %l ^| findstr "_LLVM"') do (set symbolname=%e & echo !symbolname:~1!))" What it does: For all *.lib files ina specific dir starting with LLVM call dumpbin.exe (tool from Visualstudio) and write all symbols with LLVM_ into a specific file 2017-04-05 20:40 GMT+02:00 Jakob Bornecrantz via llvm-dev &lt...

See http://wiki.scilab.org/Contributor_-_LLVM Ciao, Duncan.

...le to build a cross-compiler using your patch > (with a minor change) and ran "hello world" in Qemu-ARM after compiling and > linking it on x86_64.  I put the list of outstanding bugs on a wiki page for > tracking and reference: > http://google2.osuosl.org/wiki/index.php/HowTo:_LLVM-based_cross_compiler > > I'll try to get the patch committed to llvm-gcc piece-meal.  It looks like > part of the patch includes the fix for http://llvm.org/PR2545 -- Chris said > he's OK with the patch being committed, is there any reason it hasn't been > applied yet?  D...

...lvm-gcc4.2-2.5.source/gcc/../include > -I../../../../src/llvm-gcc4.2-2.5.source/gcc/../libcpp/include > -I../../../../src/llvm-gcc4.2-2.5.source/gcc/../libdecnumber > -I../libdecnumber -I/tmp/llvm-project/install/x86_64-arm/llvm/include > -I/tmp/llvm-project/src/llvm-2.5/include -DENABLE_LLVM > -I/tmp/llvm-project/install/x86_64-arm/llvm/include  -D_DEBUG  -D_GNU_SOURCE > -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS   -o build/gencondmd.o > build/gencondmd.c > > ../../../../src/llvm-gcc4.2-2.5.source/gcc/config/arm/arm.md:4788: error: > ‘MACHO_DYNAMIC_NO_PIC_P’ undec...

Hello Lang, so you are part of the "Jitter-Team"? I'm really interested in this whole jitting-process. I wanted to know, is there a way to load other obj-files, than the one created with clang? Could I load - for example - a obj-File from VisualStudio? Or will the namemangeling fail? Kind regards Björn From: Lang Hames <lhames at gmail.com> To: bjoern.gaier at

...ndelsregister Bad Homburg v.d.H. HRB 9816, > USt.ID-Nr. DE 114 165 789 > Geschäftsführer: Hiroshi Kawamura, Dr Hiroshi Nakamura, Markus Bode, > Heiko Lampert, Takashi Nagano, Takeshi Fukushima. > > _______________________________________________ > LLVM Developers mailing list > _llvm-dev at lists.llvm.org_ <mailto:llvm-dev at lists.llvm.org> > _http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev_ > > -- > _https://weliveindetail.github.io/blog/_ > _https://cryptup.org/pub/stefan.graenitz at gmail.com_ > > > Als GmbH eingetragen im Handelsregis...

We already half-have this, the LLVM_BUILD_LLVM_C_DYLIB cmake option builds a shared object which exports the llvm-c interface but it only works on Darwin. tools/llvm-shlib/CMakeLists.txt 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...

Hello Stefan, I'm happy someone replied to my problem! Many thanks! To be honest... I didn't understood much of your mail. I'm a beginner with the JIT - so I will explain what I've done. To manage the memory and resolve symbols, I'm using my own Resolver-Class, which overloads the allocation and the findSymbol functions. I've noticed today, that the

Hi Bjoern, I'm trying to make exceptions run. I have an Object file with a function, > throwing a 1 and a second function which should catch the 1. Normal JITTING > under Windows showed me, that I have an unresolved reference to the virtual > table of type_info. Some experiments later I was able to load "msvcrt.lib" > as an archive and could resolve the reference. Nice -