Displaying 5 results from an estimated 5 matches for "call0".
Did you mean:
call
2014 Mar 10
2
[LLVMdev] GlobalValues appear in their own use lists?
In the following IR module:
–
define i8 @foo() #0 {
entry:
%call0 = call i8 @bar()
ret i8 %call0
}
declare i8 @bar() #1
–
@bar() gets marked as its own user in top-of-tree LLVM. I patched the Verifier to check it (but didn’t commit the patch):
–
Index: lib/IR/Verifier.cpp
===================================================================
--- lib/IR/Verifier....
2014 Mar 11
3
[LLVMdev] GlobalValues appear in their own use lists?
...Assert1(*UI != &GV, "Global values cannot be their own uses!", &GV);
+ }
+
Assert1(!GV.hasAppendingLinkage() || isa<GlobalVariable>(GV),
"Only global variables can have appending linkage!", &GV);
$ cat whatever.ll
define i8 @foo() #0 {
entry:
%call0 = call i8 @bar()
ret i8 %call0
}
declare i8 @bar() #1
$ /Volumes/Excelion/lldb/llvm-build/Debug+Asserts/x86_64/Debug+Asserts/bin/llc whatever.ll
Global values cannot be their own uses!
i8 ()* @bar
LLVM ERROR: Broken module found, compilation aborted!
Sean
On Mar 10, 2014, at 3:36 PM, Chris L...
2009 Jun 08
2
[LLVMdev] Call to address 0 gets removed
Hello
If I optimize (opt -std-compile-opts ) the following .ll
; ModuleID = 'call0.ll'
target datalayout =
"e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:32:64-f32:32:32-f64:32:64-v64:64:64-v128:128:128-a0:0:64-f80:32:32"
target triple = "i386-mingw32"
define i32 @t(i32 %a) nounwind {
entry:
%0 = tail call i32 inttoptr (i32 0 to i32 (i32)*)(i32 %...
2009 Jun 09
0
[LLVMdev] Call to address 0 gets removed
On Jun 8, 2009, at 4:48 PMPDT, Marius Wachtler wrote:
> Hello
>
> If I optimize (opt -std-compile-opts ) the following .ll
>
> ; ModuleID = 'call0.ll'
> target datalayout = "e-p:32:32:32-i1:8:8-i8:8:8-i16:16:16-i32:32:32-
> i64:32:64-f32:32:32-f64:32:64-v64:64:64-v128:128:128-a0:0:64-
> f80:32:32"
> target triple = "i386-mingw32"
>
> define i32 @t(i32 %a) nounwind {
> entry:
> %0 = tail ca...
2018 Apr 19
1
xtensa backend
Can you give me some insights to implement the windowed calling convention
in this xtensa backend :
https://github.com/afonso360/llvm-xtensa/tree/xtensa/lib/Target/Xtensa ?
For now, only the simpler CALL0 calling convention is implemented.
In order to implement the windowed calling convention, every routines must
start with the ENTRY instruction which increments the register window
pointer.
Do I have to manually insert this instruction during the PrologEpilog
phase, and how can I declare this inst...