Displaying 9 results from an estimated 9 matches for "llvminitializex86targetinfo".
2013 Sep 22
2
[LLVMdev] Bad permissions for mapped region
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 sig...
2010 May 28
0
[LLVMdev] how to get TargetData?
...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 want....
2013 Sep 22
0
[LLVMdev] Bad permissions for mapped region
...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== Pr...
2010 May 28
4
[LLVMdev] how to get TargetData?
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
2010 Dec 23
1
[LLVMdev] Linking to LLVM with CMake
...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 notice...
2010 Dec 26
0
[LLVMdev] does TargetRegistry allocate heap memory?
Hi and merry X-Mas!
At initialization I add some targets (e.g. LLVMInitializeX86TargetInfo()).
Is this guaranteed not to allocate memory to prevent memory leaks?
If you use llvm in a plug-in then it is possible to load and unload the
plugin.
As there is no way to clear the target registry and I do not see a "new"
at the first glance I assume it does not allocate heap memory.
I...
2012 Mar 04
1
[LLVMdev] LLVM from .NET
I've been struggling to get LLVM to work from .NET using the llvm-fs
bindings for the past few weeks. I finally found an installation procedure
that works and documented it here:
http://fsharpnews.blogspot.com/2012/03/using-llvm-from-f-under-windows.html
The good news is that I have that program compiling the Fibonacci function
and executing it from F# all via LLVM.
However, I still have a
2017 Aug 01
2
[RFC] Profile guided section layout
...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 LLVMInitializeNVPT...
2017 Jul 31
2
[RFC] Profile guided section layout
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