Displaying 6 results from an estimated 6 matches for "constructmemberdie".
2016 Sep 10
3
DebugInfo: purpose of align field
...implementing support for DWARFv5 DW_AT_alignment attr and
I got a question about align field in debug info section of IR/Bitcode.
Currently it is being dumped almost in any case, however according to
code we use align from DI* objects only when dealing with
class/structure bitfields: DwarfUnit::constructMemberDIE.
Dumping align information everywhere only for 1 case looks like overhead
to me.
Consider the following code:
struct S {
char c;
} s;
When compiled with debug enabled in IR we get smth like that:
!6 = distinct !DICompositeType(tag: DW_TAG_structure_type, name: "S",
file: !5, lin...
2015 Jun 02
2
[LLVMdev] `Ty && "Trying to add a type that doesn't exist?
...ibc.so.6 0x00007fea3b63b83b abort + 379
5 libc.so.6 0x00007fea3b630d9e
6 libc.so.6 0x00007fea3b630e42
7 clang 0x00000000016b8252 llvm::DwarfUnit::addType(llvm::DIE&,
llvm::DIType, llvm::dwarf::Attribute) + 610
8 clang 0x00000000016b9337
llvm::DwarfUnit::constructMemberDIE(llvm::DIE&, llvm::DIDerivedType) + 135
9 clang 0x00000000016ba2ed
llvm::DwarfUnit::constructTypeDIE(llvm::DIE&, llvm::DICompositeType) + 2221
10 clang 0x00000000016b7e9c
llvm::DwarfUnit::getOrCreateTypeDIE(llvm::MDNode const*) + 412
11 clang 0x00000000016b80a9...
2015 Jun 04
2
[LLVMdev] `Ty && "Trying to add a type that doesn't exist?
...so.6 0x00007fea3b630d9e
>> 6 libc.so.6 0x00007fea3b630e42
>> 7 clang 0x00000000016b8252
>> llvm::DwarfUnit::addType(llvm::DIE&, llvm::DIType, llvm::dwarf::Attribute)
>> + 610
>> 8 clang 0x00000000016b9337
>> llvm::DwarfUnit::constructMemberDIE(llvm::DIE&, llvm::DIDerivedType) + 135
>> 9 clang 0x00000000016ba2ed
>> llvm::DwarfUnit::constructTypeDIE(llvm::DIE&, llvm::DICompositeType) + 2221
>> 10 clang 0x00000000016b7e9c
>> llvm::DwarfUnit::getOrCreateTypeDIE(llvm::MDNode const*) + 412
&...
2015 Jun 04
2
[LLVMdev] `Ty && "Trying to add a type that doesn't exist?
...libc.so.6 0x00007fea3b630e42
>>>> 7 clang 0x00000000016b8252
>>>> llvm::DwarfUnit::addType(llvm::DIE&, llvm::DIType, llvm::dwarf::Attribute) +
>>>> 610
>>>> 8 clang 0x00000000016b9337
>>>> llvm::DwarfUnit::constructMemberDIE(llvm::DIE&, llvm::DIDerivedType) + 135
>>>> 9 clang 0x00000000016ba2ed
>>>> llvm::DwarfUnit::constructTypeDIE(llvm::DIE&, llvm::DICompositeType) + 2221
>>>> 10 clang 0x00000000016b7e9c
>>>> llvm::DwarfUnit::getOrCreateType...
2016 Sep 30
2
DebugInfo: purpose of align field
...got a question about align field in debug info section of IR/Bitcode.
> Thanks for looking into this!
No problem =)
>
>> Currently it is being dumped almost in any case, however according to code we use align from DI* objects only when dealing with class/structure bitfields: DwarfUnit::constructMemberDIE.
>>
>> Dumping align information everywhere only for 1 case looks like overhead to me.
> One your patch is finished it will be used in more cases, right? :-)
My point is that we dump align information everywhere and it is
currently used only in 1 case. I am trying to make it so that...
2016 Oct 03
2
DebugInfo: purpose of align field
...section of IR/Bitcode.
> >> Thanks for looking into this!
> > No problem =)
> >>
> >>> Currently it is being dumped almost in any case, however according to
> code we use align from DI* objects only when dealing with class/structure
> bitfields: DwarfUnit::constructMemberDIE.
> >>>
> >>> Dumping align information everywhere only for 1 case looks like
> overhead to me.
> >> One your patch is finished it will be used in more cases, right? :-)
> > My point is that we dump align information everywhere and it is
> currently used...