search for: __zig_panic

Displaying 7 results from an estimated 7 matches for "__zig_panic".

2017 Sep 16
2
assertion triggered since update to llvm 5
...g --release-safe This does the equivalent of -O3 The IR that it produces; ModuleID = 'test' source_filename = "test" 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 @0 = internal unnamed_addr constant i8* getelementptr inbounds ([6 x i8], [6 x i8]* @1, i64 0, i64 0), align 8 @1 = internal unnamed_addr constant [6 x i8] c"format", align 1 @2 = internal unnamed_addr constant { i8...
2017 Sep 17
2
assertion triggered since update to llvm 5
...it produces; ModuleID = 'test' >> source_filename = "test" >> 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 >> @0 = internal unnamed_addr constant i8* getelementptr inbounds ([6 x i8], >> [6 x i8]* @1, i64 0, i64 0), align 8 >> @1 = internal unnamed_addr constant [6 x i8] c"format", align 1 >...
2017 Sep 17
4
assertion triggered since update to llvm 5
...source_filename = "test" >>>> 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 >>>> @0 = internal unnamed_addr constant i8* getelementptr inbounds ([6 x >>>> i8], [6 x i8]* @1, i64 0, i64 0), align 8 >>>> @1 = internal unnamed_addr constant [6 x i8] c...
2017 Sep 17
2
assertion triggered since update to llvm 5
...;test" >>>>> 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 >>>>> @0 = internal unnamed_addr constant i8* getelementptr inbounds ([6 x >>>>> i8], [6 x i8]* @1, i64 0, i64 0), align 8 >>>>> @1 = internal unnamed_addr con...
2017 Jun 19
2
LLVM behavior different depending on function symbol name
...er to figure if you provide a standalone repro. > Standalone repro: ; ModuleID = 'test' source_filename = "test" 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:...
2017 Jun 19
2
LLVM behavior different depending on function symbol name
...t; >> ; ModuleID = 'test' >> source_filename = "test" >> 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...
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 =