Displaying 20 results from an estimated 24 matches for "dw_tag_enumeration_typ".
Did you mean:
dw_tag_enumeration_type
2014 Jul 21
2
[LLVMdev] LTO type uniquing: ODR assertion failure
...throw an assertion failure
> assert(Ty == resolve(Ty.getRef()))
> !{i32 786436, metadata <badref>, null, metadata !"SpuPacketType", i32 102,
> i64 32, i64 32, i32 0, i32 0, null, metadata <badref>, i32 0, null, null,
> metadata !"_ZTS13SpuPacketType"} ; [ DW_TAG_enumeration_type ]
> [SpuPacketType] [line 102, size 32, align 32, offset 0] [def] [from ]
>
> There are two type nodes with the same identifier:
> !473 = metadata !{i32 786436, metadata !474, null, metadata
> !"SpuPacketType", i32 102, i64 32, i64 32, i32 0, i32 0, null, metadata
> !47...
2014 Jul 21
4
[LLVMdev] LTO type uniquing: ODR assertion failure
....getRef()))
>> > !{i32 786436, metadata <badref>, null, metadata !"SpuPacketType", i32
>> > 102,
>> > i64 32, i64 32, i32 0, i32 0, null, metadata <badref>, i32 0, null,
>> > null,
>> > metadata !"_ZTS13SpuPacketType"} ; [ DW_TAG_enumeration_type ]
>> > [SpuPacketType] [line 102, size 32, align 32, offset 0] [def] [from ]
>> >
>> > There are two type nodes with the same identifier:
>> > !473 = metadata !{i32 786436, metadata !474, null, metadata
>> > !"SpuPacketType", i32 102, i64 32,...
2014 Jul 21
2
[LLVMdev] LTO type uniquing: ODR assertion failure
On Mon, Jul 21, 2014 at 10:39 AM, Manman Ren <manman.ren at gmail.com> wrote:
>
>
>
> On Mon, Jul 14, 2014 at 11:32 AM, Manman Ren <manman.ren at gmail.com> wrote:
>>
>>
>> We still have access to types via MDNodes directly and the assertion that
>> assumes all accesses to DITypes are accessing the resolved DIType will fire
>>
>> i.e
2015 Aug 18
3
[RFC PATCH 1/2] [clang]: Add AuxAttr support
...W_AT_name : (indirect string, offset: 0xeb): my_str
...
<2><47>: Abbrev Number: 4 (DW_TAG_member)
<48> DW_AT_name : (indirect string, offset: 0xe3): x
<4c> DW_AT_type : <0x6d>
...
...
<2><5f>: Abbrev Number: 5 (DW_TAG_enumeration_type)
<60> DW_AT_name : (indirect string, offset: 0x140): .llvm.aux.attr
<64> DW_AT_byte_size : 0
<3><65>: Abbrev Number: 6 (DW_TAG_enumerator)
<66> DW_AT_name : (indirect string, offset: 0x13c): .ID
<6a> DW_AT_const_value : 1...
2016 Mar 30
2
[cfe-dev] RFC: Up front type information generation in clang and llvm
...t; during module merge time.
>>
>
> Makes sense, but wouldn't you need multiple abbreviations for each DIType,
> in order to represent DITypes formed of multiple DIEs (e.g. enums, records)?
>
> Maybe something like this would work:
>
> $1 = { DIAbbrev: 0x1234, DIBlob: DW_TAG_enumeration_type<blah> }
> $2 = { DIAbbrev: 0x5678, DIBlob: DW_TAG_enumerator<blah> }
> $3 = { DIType: <ID>, DIAbbrev: [(0, $1), (8, $2), (16, $2)], DIBlob: <8
> bytes of DW_TAG_enumeration_type attrs><8 bytes of DW_TAG_enumerator
> attrs><8 bytes of DW_TAG_enumerator a...
2016 Mar 30
0
[cfe-dev] RFC: Up front type information generation in clang and llvm
...d remember to merge these as well
> during module merge time.
>
Makes sense, but wouldn't you need multiple abbreviations for each DIType,
in order to represent DITypes formed of multiple DIEs (e.g. enums, records)?
Maybe something like this would work:
$1 = { DIAbbrev: 0x1234, DIBlob: DW_TAG_enumeration_type<blah> }
$2 = { DIAbbrev: 0x5678, DIBlob: DW_TAG_enumerator<blah> }
$3 = { DIType: <ID>, DIAbbrev: [(0, $1), (8, $2), (16, $2)], DIBlob: <8
bytes of DW_TAG_enumeration_type attrs><8 bytes of DW_TAG_enumerator
attrs><8 bytes of DW_TAG_enumerator attrs><0> }...
2016 Mar 30
0
[cfe-dev] RFC: Up front type information generation in clang and llvm
...>>
>> Makes sense, but wouldn't you need multiple abbreviations for each
>> DIType, in order to represent DITypes formed of multiple DIEs (e.g. enums,
>> records)?
>>
>> Maybe something like this would work:
>>
>> $1 = { DIAbbrev: 0x1234, DIBlob: DW_TAG_enumeration_type<blah> }
>> $2 = { DIAbbrev: 0x5678, DIBlob: DW_TAG_enumerator<blah> }
>> $3 = { DIType: <ID>, DIAbbrev: [(0, $1), (8, $2), (16, $2)], DIBlob: <8
>> bytes of DW_TAG_enumeration_type attrs><8 bytes of DW_TAG_enumerator
>> attrs><8 bytes of DW_...
2016 Mar 30
1
[cfe-dev] RFC: Up front type information generation in clang and llvm
...these as well during module merge time.
>
> Makes sense, but wouldn't you need multiple abbreviations for each DIType, in order to represent DITypes formed of multiple DIEs (e.g. enums, records)?
>
> Maybe something like this would work:
>
> $1 = { DIAbbrev: 0x1234, DIBlob: DW_TAG_enumeration_type<blah> }
> $2 = { DIAbbrev: 0x5678, DIBlob: DW_TAG_enumerator<blah> }
> $3 = { DIType: <ID>, DIAbbrev: [(0, $1), (8, $2), (16, $2)], DIBlob: <8 bytes of DW_TAG_enumeration_type attrs><8 bytes of DW_TAG_enumerator attrs><8 bytes of DW_TAG_enumerator attrs>&l...
2016 Mar 30
2
[cfe-dev] RFC: Up front type information generation in clang and llvm
On Tue, Mar 29, 2016 at 7:31 PM Peter Collingbourne <peter at pcc.me.uk> wrote:
> Thanks for sharing this. Mostly seems like a reasonable plan to me. A few
> comments below.
>
>
Thanks Peter!
> On Tue, Mar 29, 2016 at 6:00 PM, Eric Christopher via cfe-dev <
> cfe-dev at lists.llvm.org> wrote:
>
>> Hi All,
>>
>> This is something that's been
2017 Oct 01
2
load with alignment of 1 crashes from being unaligned
...32 3}
!1 = distinct !DICompileUnit(language: DW_LANG_C99, file: !2, producer:
"zig 0.0.0", isOptimized: false, runtimeVersion: 0, emissionKind:
FullDebug, enums: !3, globals: !47)
!2 = !DIFile(filename: "test", directory: ".")
!3 = !{!4, !40}
!4 = !DICompositeType(tag: DW_TAG_enumeration_type, name: "Os", scope: !5,
file: !5, line: 1, baseType: !6, size: 8, align: 8, elements: !7)
!5 = !DIFile(filename: "builtin.zig", directory:
"/home/andy/dev/zig/build/zig-cache")
!6 = !DIBasicType(name: "u6", size: 8, encoding: DW_ATE_unsigned)
!7 = !{!8, !9,...
2014 Oct 14
2
[LLVMdev] [RFC] Less memory and greater maintainability for debug info IR
...ag = 66, Count = 10930, Ops = 43720, Name = DW_TAG_rvalue_reference_type
Tag = 16, Count = 54680, Ops = 218720, Name = DW_TAG_reference_type
Tag = 23, Count = 624, Ops = 4992, Name = DW_TAG_union_type
Tag = 4, Count = 5344, Ops = 42752, Name = DW_TAG_enumeration_type
Tag = 11, Count = 360390, Ops = 1081170, Name = DW_TAG_lexical_block
Tag = 258, Count = 1, Ops = 1, Name = DW_TAG_expression
Tag = 13, Count = 73880, Ops = 299110, Name = DW_TAG_member
Tag = 58, Count = 1387, Ops = 4161, Name = DW_TAG_im...
llvm bpf debug info. Re: [RFC PATCH v4 3/3] bpf: Introduce function for outputing data to perf event
2015 Aug 12
2
llvm bpf debug info. Re: [RFC PATCH v4 3/3] bpf: Introduce function for outputing data to perf event
On 2015/8/4 3:44, Alexei Starovoitov wrote:
[SNIP]
>> I'll post 2 LLVM patches by replying this mail. Please have a look and
>> help me
>> send them to LLVM if you think my code is correct.
>
>
[SNIP]
> patch 2:
> do we really need to hack clang?
> Can you just define a function that aliases to intrinsic,
> like we do for ld_abs/ld_ind ?
> void
2015 Aug 14
2
[LLVM RFC] Add llvm.typeid.for intrinsic
This is for BPF output. BPF program output bytes to perf through a
tracepoint. For decoding such data, we need a way to describe the format
of the buffer. This patch is a try which gives each variable a unique
number by introducing a new intrinsic 'llvm.typeid.for'.
At the bottom is an example of using that intrinsic and the result
of
$ clang -target bpf -O2 -c -S ./test_typeid.c
llvm bpf debug info. Re: [RFC PATCH v4 3/3] bpf: Introduce function for outputing data to perf event
2015 Aug 12
3
llvm bpf debug info. Re: [RFC PATCH v4 3/3] bpf: Introduce function for outputing data to perf event
...ble to encode the
structure using a u64, let's still dig into dwarf.
We have another idea that we can utilize dwarf's existing feature.
For example, when __buildin_bpf_typeid() get called, define an enumerate
type in dwarf info, so you'll find:
<1><2a>: Abbrev Number: 2 (DW_TAG_enumeration_type)
<2b> DW_AT_name : (indirect string, offset: 0xec): TYPEINFO
<2f> DW_AT_byte_size : 4
<30> DW_AT_decl_file : 1
<31> DW_AT_decl_line : 3
<2><32>: Abbrev Number: 3 (DW_TAG_enumerator)
<33> DW_AT_name :...
2017 Sep 16
2
assertion triggered since update to llvm 5
...ot;, i32 3}
!1 = distinct !DICompileUnit(language: DW_LANG_C99, file: !2, producer:
"zig 0.0.0", isOptimized: true, runtimeVersion: 0, emissionKind: FullDebug,
enums: !3, globals: !12)
!2 = !DIFile(filename: "test", directory: ".")
!3 = !{!4}
!4 = !DICompositeType(tag: DW_TAG_enumeration_type, name: "GlobalLinkage",
scope: !5, file: !5, line: 138, baseType: !6, size: 8, align: 8, elements:
!7)
!5 = !DIFile(filename: "builtin.zig", directory:
"/home/andy/dev/zig/build-llvm5-debug/zig-cache")
!6 = !DIBasicType(name: "u3", size: 8, encoding: DW_ATE_...
2017 Jun 19
2
LLVM behavior different depending on function symbol name
...ot;, i32 3}
!1 = distinct !DICompileUnit(language: DW_LANG_C99, file: !2, producer:
"zig 0.0.0", isOptimized: true, runtimeVersion: 0, emissionKind: FullDebug,
enums: !3, globals: !12)
!2 = !DIFile(filename: "test", directory: ".")
!3 = !{!4}
!4 = !DICompositeType(tag: DW_TAG_enumeration_type, name: "GlobalLinkage",
scope: !5, file: !5, line: 126, baseType: !6, size: 8, align: 8, elements:
!7)
!5 = !DIFile(filename: "builtin.zig", directory:
"/home/andy/dev/zig/build/zig-cache")
!6 = !DIBasicType(name: "u8", size: 8, encoding: DW_ATE_unsigned_cha...
2017 Sep 17
2
assertion triggered since update to llvm 5
...uage: DW_LANG_C99, file: !2, producer:
>> "zig 0.0.0", isOptimized: true, runtimeVersion: 0, emissionKind: FullDebug,
>> enums: !3, globals: !12)
>> !2 = !DIFile(filename: "test", directory: ".")
>> !3 = !{!4}
>> !4 = !DICompositeType(tag: DW_TAG_enumeration_type, name:
>> "GlobalLinkage", scope: !5, file: !5, line: 138, baseType: !6, size: 8,
>> align: 8, elements: !7)
>> !5 = !DIFile(filename: "builtin.zig", directory:
>> "/home/andy/dev/zig/build-llvm5-debug/zig-cache")
>> !6 = !DIBasicType(nam...
2017 Sep 17
4
assertion triggered since update to llvm 5
...gt;>>> "zig 0.0.0", isOptimized: true, runtimeVersion: 0, emissionKind: FullDebug,
>>>> enums: !3, globals: !12)
>>>> !2 = !DIFile(filename: "test", directory: ".")
>>>> !3 = !{!4}
>>>> !4 = !DICompositeType(tag: DW_TAG_enumeration_type, name:
>>>> "GlobalLinkage", scope: !5, file: !5, line: 138, baseType: !6, size: 8,
>>>> align: 8, elements: !7)
>>>> !5 = !DIFile(filename: "builtin.zig", directory:
>>>> "/home/andy/dev/zig/build-llvm5-debug/zig-cache"...
2017 Jun 19
2
LLVM behavior different depending on function symbol name
...uage: DW_LANG_C99, file: !2, producer:
>> "zig 0.0.0", isOptimized: true, runtimeVersion: 0, emissionKind: FullDebug,
>> enums: !3, globals: !12)
>> !2 = !DIFile(filename: "test", directory: ".")
>> !3 = !{!4}
>> !4 = !DICompositeType(tag: DW_TAG_enumeration_type, name:
>> "GlobalLinkage", scope: !5, file: !5, line: 126, baseType: !6, size: 8,
>> align: 8, elements: !7)
>> !5 = !DIFile(filename: "builtin.zig", directory:
>> "/home/andy/dev/zig/build/zig-cache")
>> !6 = !DIBasicType(name: "u8&...
2017 Sep 17
2
assertion triggered since update to llvm 5
..."zig 0.0.0", isOptimized: true, runtimeVersion: 0, emissionKind:
>>>>> FullDebug, enums: !3, globals: !12)
>>>>> !2 = !DIFile(filename: "test", directory: ".")
>>>>> !3 = !{!4}
>>>>> !4 = !DICompositeType(tag: DW_TAG_enumeration_type, name:
>>>>> "GlobalLinkage", scope: !5, file: !5, line: 138, baseType: !6, size: 8,
>>>>> align: 8, elements: !7)
>>>>> !5 = !DIFile(filename: "builtin.zig", directory:
>>>>> "/home/andy/dev/zig/build-llvm5-debug...