Displaying 5 results from an estimated 5 matches for "targetmachineemittofile".
2012 Jun 30
0
[LLVMdev] llc -O# / opt -O# differences
Dimitri Tcaciuc wrote:
> Is the llc/opt difference expected?
Yes. "opt" runs the optimizers, which take LLVM IR as input and produce
LLVM IR as output. "opt -O2 -debug-pass=Arguments" will show you a list
of the individual optimizations (and analyses) that opt -O2 performs.
It's possible to run them individually (opt -scalarrepl -instcombine) to
create a list
2012 Jun 30
2
[LLVMdev] llc -O# / opt -O# differences
...%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 opt
produces something that eliminates a bunch of stack loading ops....
2018 Apr 26
1
windows ABI problem with i128?
...<anton at korobeynikov.info
> wrote:
> Most probably you need to properly specify the calling convention the
> backend is using for calling the runtime functions.
Thanks for the tip. Can you be more specific? Are you suggesting there is
some config parameter I can set before running TargetMachineEmitToFile?
Do you know what calling convention it is trying to use at the callsite?
Perhaps I can simply select a different convention from this list for the
implementation of udivti3?
http://llvm.org/docs/LangRef.html#calling-conventions
Or implement the
> stub for udivti3 that performs the necessary a...
2018 Apr 26
0
windows ABI problem with i128?
Most probably you need to properly specify the calling convention the
backend is using for calling the runtime functions. Or implement the
stub for udivti3 that performs the necessary argument lifting.
I guess there is no standard ABI document describing the intended
calling convention here, so I'd just do what mingw64 does here and
make everything here compatible.
On Thu, Apr 26, 2018 at
2018 Apr 26
2
windows ABI problem with i128?
I'm trying to use LLVM to create compiler-rt.o on Windows. I use this
command from the compiler-rt project:
[nix-shell:~/downloads/llvm-project/compiler-rt]$ clang -nostdlib -S
-emit-llvm lib/builtins/udivti3.c -g -target x86_64-windows
-DCRT_HAS_128BIT
The resulting LLVM IR is:
=================================================================
; ModuleID = 'lib/builtins/udivti3.c'