Displaying 7 results from an estimated 7 matches for "debugtrap".
2020 Mar 04
2
Continuing from dbgtrap on different targets
Hi,
I'm noticing an unexpected difference between targets when I hit a dbgtrap in the debugger. Consider this simple llvm function:
define void @do_break() {
entry:
call void @llvm.debugtrap()
ret void
}
If I compile that with llc and use lldb to launch a program that calls it, on x86_64 linux (Ubuntu 18.04), here's what I see at the stop:
Process 130404 stopped
* thread #1, name = 'doit', stop reason = signal SIGTRAP
frame #0: 0x0000000000400541 doit`do_break at...
2018 Apr 26
2
windows ABI problem with i128?
..., metadata
!DIExpression()), !dbg !57
%3 = load i128, i128* %c, align 8, !dbg !58
%4 = load i128, i128* %b, align 8, !dbg !60
%5 = icmp ne i128 %3, %4, !dbg !61
br i1 %5, label %Then, label %Else, !dbg !61
Then: ; preds = %Entry
call void @llvm.debugtrap(), !dbg !62
br label %EndIf, !dbg !64
Else: ; preds = %Entry
br label %EndIf, !dbg !64
EndIf: ; preds = %Else, %Then
call void @ExitProcess(i32 0), !dbg !65
unreachable, !dbg !65
}
; Function Attrs: no...
2018 Apr 26
0
windows ABI problem with i128?
...!57
> %3 = load i128, i128* %c, align 8, !dbg !58
> %4 = load i128, i128* %b, align 8, !dbg !60
> %5 = icmp ne i128 %3, %4, !dbg !61
> br i1 %5, label %Then, label %Else, !dbg !61
>
> Then: ; preds = %Entry
> call void @llvm.debugtrap(), !dbg !62
> br label %EndIf, !dbg !64
>
> Else: ; preds = %Entry
> br label %EndIf, !dbg !64
>
> EndIf: ; preds = %Else, %Then
> call void @ExitProcess(i32 0), !dbg !65
> unreach...
2018 Apr 26
1
windows ABI problem with i128?
...8* %c, align 8, !dbg !58
> > %4 = load i128, i128* %b, align 8, !dbg !60
> > %5 = icmp ne i128 %3, %4, !dbg !61
> > br i1 %5, label %Then, label %Else, !dbg !61
> >
> > Then: ; preds = %Entry
> > call void @llvm.debugtrap(), !dbg !62
> > br label %EndIf, !dbg !64
> >
> > Else: ; preds = %Entry
> > br label %EndIf, !dbg !64
> >
> > EndIf: ; preds = %Else, %Then
> > call void @ExitProc...
2017 Jun 19
2
LLVM behavior different depending on function symbol name
...t;
target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
target triple = "x86_64-unknown-linux-gnu"
%"[]u8" = type { i8*, i64 }
@__zig_panic_implementation_provided = internal unnamed_addr constant i1
true, align 1
; Function Attrs: nounwind
declare void @llvm.debugtrap() #0
; Function Attrs: argmemonly nounwind
declare void @llvm.memcpy.p0i8.p0i8.i64(i8* nocapture writeonly, i8*
nocapture readonly, i64, i32, i1) #1
; Function Attrs: argmemonly nounwind
declare void @llvm.memset.p0i8.i64(i8* nocapture writeonly, i8, i64, i32,
i1) #1
; Function Attrs: nobuiltin...
2017 Jun 19
2
LLVM behavior different depending on function symbol name
...gt; target triple = "x86_64-unknown-linux-gnu"
>>
>> %"[]u8" = type { i8*, i64 }
>>
>> @__zig_panic_implementation_provided = internal unnamed_addr constant i1
>> true, align 1
>>
>> ; Function Attrs: nounwind
>> declare void @llvm.debugtrap() #0
>>
>> ; Function Attrs: argmemonly nounwind
>> declare void @llvm.memcpy.p0i8.p0i8.i64(i8* nocapture writeonly, i8*
>> nocapture readonly, i64, i32, i1) #1
>>
>> ; Function Attrs: argmemonly nounwind
>> declare void @llvm.memset.p0i8.i64(i8* nocapture...
2017 Jun 19
4
LLVM behavior different depending on function symbol name
Greetings,
I have a Zig implementation of ceil which is emitted into LLVM IR like this:
; Function Attrs: nobuiltin nounwind
define internal fastcc float @ceil(float) unnamed_addr #3 !dbg !644 {
Entry:
%x = alloca float, align 4
store float %0, float* %x
call void @llvm.dbg.declare(metadata float* %x, metadata !649, metadata
!494), !dbg !651
%1 = load float, float* %x, !dbg !652
%2 =