Displaying 9 results from an estimated 9 matches for "schlunki".
Did you mean:
schlunke
2010 Feb 11
1
[LLVMdev] Debugging of LLVM-IR
Sebastian Schlunke <schlunki at cs.tu-berlin.de> writes:
> I suspected something like that. :(
>
> I was hoping i could run the program and step throught IR-Code line by line, maybe even have a look at the variables.
>
> Well, what about compiling it into assembler-code. Is there any way
> to know which I...
2010 Feb 09
0
[LLVMdev] Debugging of LLVM-IR
I suspected something like that. :(
I was hoping i could run the program and step throught IR-Code line by line, maybe even have a look at the variables.
Well, what about compiling it into assembler-code. Is there any way to know which IR-line generated which assembler line(s)? (I do not need any optimizations or whatever, if that helps...)
Sebastian
On Tuesday 09 February 2010 18:45:56 you
2010 Feb 09
3
[LLVMdev] Debugging of LLVM-IR
Unfortunately, the current gdb support doesn't include line numbers.
It'll tell you what function it crashed in and the stack trace though.
Line numbers will probably come when the llvm-mc project is merged into the JIT.
On Tue, Feb 9, 2010 at 9:37 AM, Garrison Venn <gvenn.cfe.dev at gmail.com> wrote:
> Are you running this in a JIT? If so this will help:
2010 Mar 19
2
[LLVMdev] Use of blockadress() crashes llc in some cases
Hi!
In some cases the use of blockaddress() crashes llc.
I've attached two test-cases, one that crashes and for reference a slightly modified one (just 2 lines are commented) that works.
I compile the files with
# llvm-as test_crash.ll -o - | llc -f -o temp.s -
and get
0 llc 0x0000000000c6ab6f
1 llc 0x0000000000c6b38d
2 libpthread.so.0 0x00007feccd2270f0
3
2010 Feb 09
2
[LLVMdev] Debugging of LLVM-IR
Hello,
is there any way to debug a program in LLVM-IR line-by-line (i.e. with gdb)?
The problem is, i have a program in human-readable-intermediate representation that segfaults, when executed. I want to know, which line in the IR causes this.
Any help is appreciated.
Best regards,
Sebastian
2010 Feb 26
1
[LLVMdev] lli --force-interpreter does not find external function
Hello everyone,
I'm trying to run a LLVM-Bytecode-file in the interpreter (lli --force-interpreter), but i'm getting the following error-message:
LLVM ERROR: Tried to execute an unknown external function: i8* (i32)* malloc
My program is calling malloc. If I omit --force-interpreter everything runs as expected. Compiling to Assembler also works without problems. I have compiled LLVM with
2010 Mar 15
1
[LLVMdev] LLVM tries to remove labels used in blockaddress()
Works like a charm! Thanks for the fast help. :)
- Sebastian
On Monday 15 March 2010 20:10:54 you wrote:
>
> On Mar 15, 2010, at 10:01 AM, Sebastian Schlunke wrote:
>
> > I see. But the block does not necessarily contain dead code.
>
> This case is now fixed in r98566, I will fix the 'dead block' case in a bit.
>
> -Chris
>
> >
> > My
2010 Mar 15
3
[LLVMdev] LLVM tries to remove labels used in blockaddress()
Hi,
i ran into a problem when using blockaddress() with a label in another function. It seems to me that LLVM tries to remove the label used in blockaddress because it seems like it is not used, but in fact it may be used somewhere with a indirectbr.
I attached a small test-case that produces this error. (The original problem is much more complicated, so i hope the reduced example, which has no
2010 Mar 15
3
[LLVMdev] LLVM tries to remove labels used in blockaddress()
I see. But the block does not necessarily contain dead code.
My original problem is more like this:
define i32 @main() {
entry:
%target = bitcast i8* blockaddress(@test_fun, %test_label) to i8*
call i32 @test_fun(i8* %target)
ret i32 0
}
define i32 @test_fun(i8* %target) {
entry:
indirectbr i8* %target, [label %test_label]
test_label:
; assume some code here...
br label %ret
ret:
ret