search for: llvminitializex86target

...by specifying the Cdecl calling convention but the warnings persist on my (x86 Win 7) netbook. Secondly, the performance is awful which (IIRC) is probably because the native target has not been initialized correctly and LLVM is falling back to the IR interpreter. Keith Sheppard used a hack to call LLVMInitializeX86Target but that hasn't done the trick and I cannot figure out how to call the correct LLVMInitializeNativeTarget function from .NET. Does anyone know the solutions to these problems or, better yet, have a pre-existing .NET binding to LLVM where everything just works effortlessly? FWIW, I tried runni...

On Dec 23, 2014, at 10:28 AM, Chris Bieneman <beanz at apple.com> wrote: >>> It should be straight-forward to have something like LLVMInitializeX86Target/RegisterTargetMachine install the intrinsics into a registry. >> >> I tried doing that a few years ago. It’s not nearly as easy as it sounds because we’ve got hardcoded references to various target intrinsics scattered throughout the code. > > I was just writing to say exactly t...

...r design here: we should move to a model where intrinsic tables are registered by any targets that are activated. That would allow the intrinsic tables (including these switch/lookup mapping tables) to be in the target that uses them. > > It should be straight-forward to have something like LLVMInitializeX86Target/RegisterTargetMachine install the intrinsics into a registry. I tried doing that a few years ago. It’s not nearly as easy as it sounds because we’ve got hardcoded references to various target intrinsics scattered throughout the code. -------------- next part -------------- An HTML attachment was s...

Hi List, I'm trying to upgrade our llvm-c based compiler from JIT to MCJIT. While trying to do so I encountered several problems. Looks like C API does not have proper functions to intialize LLVM with MCJIT. I ended up wrapping the following functions in my own init routine. LLVMInitializeX86TargetInfo(); LLVMInitializeX86Target(); LLVMInitializeX86TargetMC(); LLVMInitializeX86AsmPrinter(); LLVMInitializeX86AsmParser(); With this set of functions it attempts to JIT something at least. I run into a segfault, valgrind reports the following: ==27130== Process terminating with default action of...

...ple const std::string FeatureStr = ""; // hard coded for example std::string Err; const Target* T; TargetMachine* TM = NULL; const TargetData* TD; // Or just call InitializeAllTargetInfos() and InitializeAllTargets() for all targets enabled by your LLVM build. LLVMInitializeX86TargetInfo(); LLVMInitializeX86Target(); T = TargetRegistry::lookupTarget(TripleStr, Err); if(!Err.empty()) // error handling // Create TargetMachine TM = T->createTargetMachine(TripleStr, FeatureStr); if(TM == NULL) // error handling // TD is what you wan...

...gt; I'm trying to upgrade our llvm-c based compiler from JIT to MCJIT. > While trying to do so I encountered several problems. Looks like C > API does not have proper functions to intialize LLVM with MCJIT. > I ended up wrapping the following functions in my own init routine. > > LLVMInitializeX86TargetInfo(); > LLVMInitializeX86Target(); > LLVMInitializeX86TargetMC(); > LLVMInitializeX86AsmPrinter(); > LLVMInitializeX86AsmParser(); > > With this set of functions it attempts to JIT something at least. > I run into a segfault, valgrind reports the following: > > ==27130=...

...chine subclass entirely, and use X86_32TargetMachine for the 64-bit target. And the 16-bit target too. And nothing seems to have broken AFAICT... --- a/lib/Target/X86/X86TargetMachine.cpp +++ b/lib/Target/X86/X86TargetMachine.cpp @@ -24,8 +24,9 @@ using namespace llvm; extern "C" void LLVMInitializeX86Target() { // Register the target. + RegisterTargetMachine<X86_32TargetMachine> W(TheX86_16Target); RegisterTargetMachine<X86_32TargetMachine> X(TheX86_32Target); - RegisterTargetMachine<X86_64TargetMachine> Y(TheX86_64Target); + RegisterTargetMachine<X86_32TargetMachine>...

Dear all I am trying to get the size of an LLVM pointer type. getPrimitiveSizeInBits() returns 0 for it and the documentation for isSized() suggest to use TargetData. I figured out from Kaleidoscope example that one can get a pointer to TagetData object through the execution engine but it seems to be an overkill. What is the right way to do it? Best regards, Victor -------------- next part

...2_12DenseSetPairIS1_EEE4growEj _Znwm 2 _ZN4llvm14object_creatorINS_2cl10SubCommandEE4callEv _Znwm 2 _ZNSt6vectorISt4pairIPFvPvES1_ESaIS4_EE19_M_emplace_back_auxIJS4_EEEvDpOT_ _Znwm 2 _ZNSt6vectorINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESaIS5_EE19_M_emplace_back_auxIJS5_EEEvDpOT_ _Znwm 2 LLVMInitializeX86TargetInfo __cxa_guard_release 2 LLVMInitializeRISCVTargetInfo __cxa_guard_release 2 LLVMInitializeNVPTXTargetInfo __cxa_guard_release 2 LLVMInitializeAMDGPUTargetInfo __cxa_guard_release 2 LLVMInitializeX86TargetInfo __cxa_guard_acquire 2 LLVMInitializeRISCVTargetInfo __cxa_guard_acquire 2 LLVMInitialize...

A rebased version of the lld patch is attached. Cheers, Rafael On 31 July 2017 at 15:11, Rafael Avila de Espindola <rafael.espindola at gmail.com> wrote: > Tobias Edler von Koch <tobias at codeaurora.org> writes: > >> Hi Rafael, >> >> On 07/31/2017 04:20 PM, Rafael Avila de Espindola via llvm-dev wrote: >>> However, do we need to start with

Circling back to Chandler on file size differences. Here are the highlights of what is different. For my analysis I built LLVM and Clang using a clang built with my patches. The same clang was used for the baseline and the stripped build. I used the following CMake command: cmake -G "Sublime Text 2 - Ninja" -DCMAKE_BUILD_TYPE=Release -DLLVM_BUILD_LLVM_DYLIB=Yes

...any JITting. Unfortunately, LLVMInitializeNativeTarget is defined static inline and does not appear in the .a files; thus a client not written in C or C++ trying to JIT cannot link to the library and call LLVMInitializeNativeTarget that way. It can call a target-specific library function such as LLVMInitializeX86Target, but this is obviously not portable.

...mpiled fine. The build fails, complaining of: CMakeFiles/nvm.dir/main.cpp.o: In function `global constructors keyed to main': main.cpp:(.text+0x41): undefined reference to `LLVMLinkInJIT' CMakeFiles/nvm.dir/main.cpp.o: In function `main': main.cpp:(.text+0x55): undefined reference to `LLVMInitializeX86TargetInfo' main.cpp:(.text+0x5a): undefined reference to `LLVMInitializeX86Target' ... When I try "jit" in place of "engine" in llvm_config, it complains that "jit" is not an llvm component. Is there a straight-forward tutorial on how to use CMake with LLVM? (I no...

This is from https://stackoverflow.com/questions/48360685/no-targets-in-targetregistry I have the following code, which should get the default llvm::Target. auto const targetTriple = llvm::sys::getDefaultTargetTriple(); llvm_module.setTargetTriple(targetTriple); std::string error; auto const * target = llvm::TargetRegistry::lookupTarget(targetTriple, error); if (target ==

Hello All, I'm building an F# binding for LLVM and it seems to be working for the parts of Core and BitWriter that I've tested but I've hit problems with Target/ExecutionEngine. The following test code works with the initializeNativeTarget line commented out like so: <https://github.com/keithshep/llvm-fs/blob/b7050b841108dc703e58563a4cff8845603c950d/test/simpletest2.fs> ...

...1 AM, Chris Lattner <clattner at apple.com <mailto:clattner at apple.com>> wrote: >> >> On Dec 23, 2014, at 10:28 AM, Chris Bieneman <beanz at apple.com <mailto:beanz at apple.com>> wrote: >>>>> It should be straight-forward to have something like LLVMInitializeX86Target/RegisterTargetMachine install the intrinsics into a registry. >>>> >>>> I tried doing that a few years ago. It’s not nearly as easy as it sounds because we’ve got hardcoded references to various target intrinsics scattered throughout the code. >>> >>> I w...

...6baJtJvuCJwbJ6fYi5rwoP3=dNA9DCBZtT7mwA at mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Not sure. But when doing this in the C-Api, you've to initialize/add the > Targets first. It'll not run with all buildin-targets by default. > As an example: LLVMInitializeX86Target > <http://llvm.org/doxygen/X86TargetMachine_8cpp_source.html#l00068> > This is for the C-API, so i think similar things apply to the C++ API the > C-API is based on. > > 2018-01-20 22:32 GMT+01:00 Brent Lewis via llvm-dev <llvm-dev at lists.llvm.org >>: > >> T...