Displaying 9 results from an estimated 9 matches for "llvmcreatetargetmachin".
Did you mean:
llvmcreatetargetmachine
2012 Dec 26
1
[LLVMdev] Proper values for LLVMCreateTargetMachine
I can't seem to get LLVMCreateTargetMachine to work on my box (MBP i7 OS X
10.8). What should the values of triple, cpu and features be? I'm just
looking for a way to get this up and going for now, I don't need specific
optimizations.
No matter what I send the function, I always get nil back. I'm giving it
LLVMGetFirstTarget as...
2017 Sep 19
2
What is the correct Targettripple for generating a X86 COFF-Files on windows?
Just got started and stuck at the same time. Working with the C-Api, i have
come to the point where i want to emit a binary file for my module. I
queried the X86-Target and called LLVMCreateTargetMachine this way:
> LTarget := LLVMGetTargetFromName('x86');
> LMachine := LLVMCreateTargetMachine(LTarget, 'i386-win32-msvc', nil,
> nil, LLVMCodeGenLevelDefault, LLVMRelocDefault, LLVMCodeModelDefault);
>
A call to LLVMTargetMachineEmitToFile using LLVMObjectFi...
2017 Sep 19
0
What is the correct Targettripple for generating a X86 COFF-Files on windows?
...quot;windows"
2017-09-19 19:09 GMT+02:00 Alexander Benikowski <sebal007 at googlemail.com>:
> Just got started and stuck at the same time. Working with the C-Api, i
> have come to the point where i want to emit a binary file for my module. I
> queried the X86-Target and called LLVMCreateTargetMachine this way:
>
>> LTarget := LLVMGetTargetFromName('x86');
>> LMachine := LLVMCreateTargetMachine(LTarget, 'i386-win32-msvc',
>> nil, nil, LLVMCodeGenLevelDefault, LLVMRelocDefault, LLVMCodeModelDefault);
>>
>
> A call to LLVMTargetMachine...
2017 Sep 30
2
invalid code generated on Windows x86_64 using skylake-specific features
...if (g->is_native_target) {
target_specific_cpu_args = ZigLLVMGetHostCPUName();
target_specific_features = ZigLLVMGetNativeFeatures();
} else {
target_specific_cpu_args = "";
target_specific_features = "";
}
g->target_machine = LLVMCreateTargetMachine(target_ref,
buf_ptr(&g->triple_str),
target_specific_cpu_args, target_specific_features, opt_level,
reloc_mode, LLVMCodeModelDefault);
char *ZigLLVMGetHostCPUName(void) {
std::string str = sys::getHostCPUName();
return strdup(str.c_str());
}
char *ZigLLVMGetNativeFea...
2017 Oct 01
1
invalid code generated on Windows x86_64 using skylake-specific features
...target_specific_cpu_args = ZigLLVMGetHostCPUName();
> target_specific_features = ZigLLVMGetNativeFeatures();
> } else {
> target_specific_cpu_args = "";
> target_specific_features = "";
> }
>
> g->target_machine = LLVMCreateTargetMachine(target_ref,
> buf_ptr(&g->triple_str),
> target_specific_cpu_args, target_specific_features, opt_level,
> reloc_mode, LLVMCodeModelDefault);
>
>
>
> char *ZigLLVMGetHostCPUName(void) {
> std::string str = sys::getHostCPUName();
> return strdup(...
2017 Oct 03
2
invalid code generated on Windows x86_64 using skylake-specific features
...;
>>> target_specific_features = ZigLLVMGetNativeFeatures();
>>> } else {
>>> target_specific_cpu_args = "";
>>> target_specific_features = "";
>>> }
>>>
>>> g->target_machine = LLVMCreateTargetMachine(target_ref,
>>> buf_ptr(&g->triple_str),
>>> target_specific_cpu_args, target_specific_features,
>>> opt_level, reloc_mode, LLVMCodeModelDefault);
>>>
>>>
>>>
>>> char *ZigLLVMGetHostCPUName(void) {
>>>...
2014 Jun 16
2
[LLVMdev] Regression in 3.4's register allocator?
Yep, quite right, Evan. Any regalloc differences due to that patch are purely coincidence;
-Jim
> On Jun 16, 2014, at 10:13 AM, Evan Cheng <evan.cheng at apple.com> wrote:
>
> Hi Niklas,
>
> The attached patch has nothing to do with register allocation. r206094 changes how cpu auto-detection is done. I believe it's now the responsibility of the tools (e.g. llc) to
2012 Jun 30
2
[LLVMdev] llc -O# / opt -O# differences
...tproc
## BB#0: ## %entry
movq %rdi, -24(%rsp)
movq %rsi, -16(%rsp)
movq -24(%rsp), %rax
movsd (%rax), %xmm0
subsd (%rsi), %xmm0
movsd %xmm0, -8(%rsp)
mulsd %xmm0, %xmm0
ret
.cfi_endproc
This matches the results of LLVMCreateTargetMachine with
CodeGenLevelAggressive followed by LLVMTargetMachineEmitToFile which
I'm using.
.
Is the llc/opt difference expected? I'm a bit confused since I'd
expect same -O level running the same optimization passes. I have to
admit I'm not well versed in assembly but to me it looks like...
2014 Aug 05
2
[LLVMdev] LLVM as a shared library
On Tue, Aug 5, 2014 at 2:57 PM, Filip Pizlo <fpizlo at apple.com> wrote:
>
> On Aug 5, 2014, at 2:51 PM, Eric Christopher <echristo at gmail.com> wrote:
>
> On Tue, Aug 5, 2014 at 2:49 PM, Filip Pizlo <fpizlo at apple.com> wrote:
>
>
> On Aug 5, 2014, at 1:46 PM, Eric Christopher <echristo at gmail.com> wrote:
>
> (7) Make the C API truly great.