search for: basicblock0

Displaying 6 results from an estimated 6 matches for "basicblock0".

Did you mean: basicblock
2018 Aug 20
2
Windows "0xC00001A5: An invalid exception handler routine has been detected" with LLVM win32 (i386) SEH code
...alid exception handler routine has been detected (parameters: 0x00000001). With some fairly simple SEH enabled routine: define i32 @__elements_entry_point_main(%._gt2a_RemObjects_d_Elements_d_System_d_Array_t_1s*) #0 personality i8* bitcast (i32 ()* @_elements_exception_handler to i8*) !dbg !61 { BasicBlock0: %1 = alloca %._gt2a_RemObjects_d_Elements_d_System_d_Array_t_1s* store %._gt2a_RemObjects_d_Elements_d_System_d_Array_t_1s* %0, %._gt2a_RemObjects_d_Elements_d_System_d_Array_t_1s** %1 call void @llvm.dbg.declare(metadata %._gt2a_RemObjects_d_Elements_d_System_d_Array_t_1s** %1, metadata !86...
2018 Aug 20
2
Windows "0xC00001A5: An invalid exception handler routine has been detected" with LLVM win32 (i386) SEH code
...0001).>> >> With some fairly simple SEH enabled routine: >> >> define i32 @__elements_entry_point_main(%._gt2a_RemObjects_d_Elemen- >> ts_d_System_d_Array_t_1s*) #0 personality i8* bitcast (i32 ()* >> @_elements_exception_handler to i8*) !dbg !61 {>> BasicBlock0: >> %1 = alloca %._gt2a_RemObjects_d_Elements_d_System_d_Array_t_1s* >> store %._gt2a_RemObjects_d_Elements_d_System_d_Array_t_1s* %0, >> %._gt2a_RemObjects_d_Elements_d_System_d_Array_t_1s** %1>> call void @llvm.dbg.declare(metadata >> %._gt2a_RemObject...
2016 Dec 21
2
debug info "ref" parameter
...meter register it shows the actual pointer value of the debug register, instead of the value it refers to. This works fine if the llvm.debug.declare points to a local alloca, how can this be and how can I make it work so both show the integer value directly? define void @test1(i32) #0 !dbg !5 { BasicBlock0: %1 = alloca i32 store i32 %0, i32* %1 call void @llvm.dbg.declare(metadata i32* %1, metadata !20, metadata !22), !dbg !23 // This one is fine %2 = load i32, i32* %1, !dbg !24 %3 = add i32 %2, 1, !dbg !24 store i32 %3, i32* %1, !dbg !24 ret void, !dbg !25 } define void @ms_t1...
2016 Dec 21
0
debug info "ref" parameter
...e actual pointer value of the debug > register, instead of the value it refers to. This works fine if the > llvm.debug.declare points to a local alloca, how can this be and how can > I make it work so both show the integer value directly? > > define void @test1(i32) #0 !dbg !5 { > BasicBlock0: > %1 = alloca i32 > store i32 %0, i32* %1 > call void @llvm.dbg.declare(metadata i32* %1, metadata !20, metadata > !22), !dbg !23 > // This one is fine > %2 = load i32, i32* %1, !dbg !24 > %3 = add i32 %2, 1, !dbg !24 > store i32 %3, i32* %1, !dbg !24 >...
2016 Dec 21
2
debug info "ref" parameter
...e debug >> register, instead of the value it refers to. This works fine if the >> llvm.debug.declare points to a local alloca, how can this be and how >can >> I make it work so both show the integer value directly? >> >> define void @test1(i32) #0 !dbg !5 { >> BasicBlock0: >> %1 = alloca i32 >> store i32 %0, i32* %1 >> call void @llvm.dbg.declare(metadata i32* %1, metadata !20, >metadata >> !22), !dbg !23 >> // This one is fine >> %2 = load i32, i32* %1, !dbg !24 >> %3 = add i32 %2, 1, !dbg !24 >>...
2016 Dec 22
0
debug info "ref" parameter
...e actual pointer value of the debug > register, instead of the value it refers to. This works fine if the > llvm.debug.declare points to a local alloca, how can this be and how can > I make it work so both show the integer value directly? > > define void @test1(i32) #0 !dbg !5 { > BasicBlock0: > %1 = alloca i32 > store i32 %0, i32* %1 > call void @llvm.dbg.declare(metadata i32* %1, metadata !20, metadata > !22), !dbg !23 > // This one is fine > %2 = load i32, i32* %1, !dbg !24 > %3 = add i32 %2, 1, !dbg !24 > store i32 %3, i32* %1, !dbg !24 >...