Displaying 5 results from an estimated 5 matches for "dw_ate_float".
2015 Nov 01
4
Representing X86 long double in Debug Info
...e (128)
call void @llvm.dbg.declare(metadata x86_fp80* %x, metadata !11, metadata
!13), !dbg !14
%x = alloca x86_fp80, align 16
!11 = !DILocalVariable(name: "x", scope: !4, file: !1, line: 2, type: !12)
!12 = !DIBasicType(name: "long double", size: 128, align: 128, encoding:
DW_ATE_float)
!13 = !DIExpression()
which happens because llvm knows that fp80s are 80bits, while clang
declares them as 128bits in the debug info. We might have to special case
this in the verifier, but before we do that, I wanted to ask about the
following:
Reading the DWARF standard, it seems like the foll...
2017 Nov 15
2
workaround for debug info bug?
...e: "Foo", scope:
!30, file: !5, line: 1, size: 32, align: 32, elements: !31)
!31 = !{!32, !34}
!32 = !DIDerivedType(tag: DW_TAG_member, name: "float", scope: !30, file:
!5, line: 2, baseType: !33, size: 32, align: 32)
!33 = !DIBasicType(name: "f32", size: 32, encoding: DW_ATE_float)
!34 = !DIDerivedType(tag: DW_TAG_member, name: "int", scope: !30, file: !5,
line: 3, baseType: !35, size: 32, align: 32)
!35 = !DIBasicType(name: "u32", size: 32, encoding: DW_ATE_unsigned)
!36 = !DILocation(line: 7, column: 5, scope: !29)
!37 = !DILocation(line: 6, column: 19,...
2017 Jun 19
2
LLVM behavior different depending on function symbol name
...distinct !DISubprogram(name: "ceil", scope: !17, file: !17, line: 3,
type: !47, isLocal: true, isDefinition: true, scopeLine: 3, isOptimized:
true, unit: !1, variables: !50)
!47 = !DISubroutineType(types: !48)
!48 = !{!49, !49}
!49 = !DIBasicType(name: "f32", size: 32, encoding: DW_ATE_float)
!50 = !{!51}
!51 = !DILocalVariable(name: "x", arg: 1, scope: !52, file: !17, line: 3,
type: !49)
!52 = distinct !DILexicalBlock(scope: !46, file: !17, line: 3, column: 13)
!53 = !DILocation(line: 3, column: 13, scope: !52)
!54 = !DILocation(line: 6, column: 36, scope: !55)
!55 = distinc...
2017 Jun 19
2
LLVM behavior different depending on function symbol name
..., scope: !17, file: !17, line:
>> 3, type: !47, isLocal: true, isDefinition: true, scopeLine: 3, isOptimized:
>> true, unit: !1, variables: !50)
>> !47 = !DISubroutineType(types: !48)
>> !48 = !{!49, !49}
>> !49 = !DIBasicType(name: "f32", size: 32, encoding: DW_ATE_float)
>> !50 = !{!51}
>> !51 = !DILocalVariable(name: "x", arg: 1, scope: !52, file: !17, line: 3,
>> type: !49)
>> !52 = distinct !DILexicalBlock(scope: !46, file: !17, line: 3, column: 13)
>> !53 = !DILocation(line: 3, column: 13, scope: !52)
>> !54 = !DIL...
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 =