search for: debug_pubtyp

Hello all, I am implementing support for .debug_names section (which is introduced in DWARFv5 standard as replacement for .debug_pubnames and .debug_pubtypes). The question is: should usage of DWARF version 5 force generation of .debug_names instead of .debug_pubnames or we can make it just default behavior and provide user with the interface (cmd switch) to use other DWARFv5 features but generate old .debug_pubnames and .debug_pubtypes? The thing...

...hat has a class A that inherits from > class B, but only a forward declaration of class B is provided. Hmm do we emit that kind of thing today? In a naïve test, I'm seeing the full description of class B. > - LLDB wants the .apple_XXX accelerator tables, GDB wants > .debug_pubnames/.debug_pubtypes Agreed. > So it would be great to have a "-debugger" flag that could be specified > > -debugger=lldb > -debugger=gdb > > Not sure on the option name, but I do like the idea. We'll bikeshed the name later but yes, that's the plan. Thanks, --paulr > &gt...

...0000 0000000000000000 0000000000000000 000020bb 2**0 29 .debug_macinfo 00000000 0000000000000000 0000000000000000 000020cf 2**0 30 .debug_line 00000053 0000000000000000 0000000000000000 000020e3 2**0 31 .debug_loc 00000000 0000000000000000 0000000000000000 0000213e 2**0 32 .debug_pubtypes 00000000 0000000000000000 0000000000000000 00002152 2**0 33 .debug_str 00000069 0000000000000000 0000000000000000 00002166 2**0 34 .debug_ranges 00000000 0000000000000000 0000000000000000 000021d9 2**0 $ ./bin/llvm-objdump -h a.out | grep debug 27 .zdebug_info 00000058 00000000...

...obsolete debug info which refers to code deleted by the linker     doing the garbage collection (gc-sections).   - Deduplicate debug type definitions for reducing resulting size of binary.   - Build accelerator/index tables.     = .debug_aranges, .debug_names, .gdb_index, .debug_pubnames, .debug_pubtypes.   - Strip unneeded tables.     = .debug_aranges, .debug_names, .gdb_index, .debug_pubnames, .debug_pubtypes.   - Compress or decompress debug info as requested. Possible feature:   - Join split dwarf .dwo files in a single file containing all debug info     (convert split DWARF into mo...

...ebug-info or some flag like that. I think the option is -f(no-)standalone-debug-info which only emits full definitions of classes in the object file that holds and object’s vtable. -- adrian > >>> - LLDB wants the .apple_XXX accelerator tables, GDB wants >>> .debug_pubnames/.debug_pubtypes >> >> Agreed. >> >>> So it would be great to have a "-debugger" flag that could be specified >>> >>> -debugger=lldb >>> -debugger=gdb >>> >>> Not sure on the option name, but I do like the idea. >> >&g...

...     doing the garbage collection (gc-sections). > >    - Deduplicate debug type definitions for reducing resulting > size of > binary. > >    - Build accelerator/index tables. >      = .debug_aranges, .debug_names, .gdb_index, .debug_pubnames, > .debug_pubtypes. > >    - Strip unneeded tables. >      = .debug_aranges, .debug_names, .gdb_index, .debug_pubnames, > .debug_pubtypes. > >    - Compress or decompress debug info as requested. > > Possible feature: > >    - Join split dwarf .dwo files in a si...

...     doing the garbage collection (gc-sections). > >    - Deduplicate debug type definitions for reducing resulting > size of > binary. > >    - Build accelerator/index tables. >      = .debug_aranges, .debug_names, .gdb_index, .debug_pubnames, > .debug_pubtypes. > >    - Strip unneeded tables. >      = .debug_aranges, .debug_names, .gdb_index, .debug_pubnames, > .debug_pubtypes. > >    - Compress or decompress debug info as requested. > > Possible feature: > >    - Join split dwarf .dwo files in a si...

...ons weren’t really helpful, so they were removed. > > which only emits full definitions of classes in the object file that holds and object’s vtable. > > -- adrian > > > >>> - LLDB wants the .apple_XXX accelerator tables, GDB wants > >>> .debug_pubnames/.debug_pubtypes > >> > >> Agreed. > >> > >>> So it would be great to have a "-debugger" flag that could be specified > >>> > >>> -debugger=lldb > >>> -debugger=gdb > >>> > >>> Not sure on the option name,...

.... That's something that GDB insists on having. (It turns out that the standard operator was defined in DWARF 3, so we also have to emit the GNU operator if we're producing DWARF 2. Tuning considerations don't trump what the standard says.) Another example would be .debug_pubnames and .debug_pubtypes sections. Currently these default to omitted for Darwin and PS4, but included everywhere else. My initial patch for "tuning" changes the PS4 platform criterion to the SCE debugger predicate; quite likely the "not Darwin" criterion ought to be "not LLDB" or in other w...

...   - Deduplicate debug type definitions for reducing >> resulting size of >> binary. >> >>    - Build accelerator/index tables. >>      = .debug_aranges, .debug_names, .gdb_index, >> .debug_pubnames, >> .debug_pubtypes. >> >>    - Strip unneeded tables. >>      = .debug_aranges, .debug_names, .gdb_index, >> .debug_pubnames, >> .debug_pubtypes. >> >>    - Compress or decompress debug info as requested. >> >> Pos...

...{ *(.debug_aranges) } .zdebug_aranges BLOCK(__section_alignment__) (NOLOAD) : { *(.zdebug_aranges) } .debug_pubnames BLOCK(__section_alignment__) (NOLOAD) : { *(.debug_pubnames) } .zdebug_pubnames BLOCK(__section_alignment__) (NOLOAD) : { *(.zdebug_pubnames) } .debug_pubtypes BLOCK(__section_alignment__) (NOLOAD) : { *(.debug_pubtypes) } .zdebug_pubtypes BLOCK(__section_alignment__) (NOLOAD) : { *(.zdebug_pubtypes) } /* DWARF 2. */ .debug_info BLOCK(__section_alignment__) (NOLOAD) : { *(.debug_info .gnu.linkonce.wi.*) } .zdebug_info BL...

...t; 29 .debug_macinfo 00000000 0000000000000000 0000000000000000 000020cf >> 2**0 >> 30 .debug_line 00000053 0000000000000000 0000000000000000 000020e3 >> 2**0 >> 31 .debug_loc 00000000 0000000000000000 0000000000000000 0000213e >> 2**0 >> 32 .debug_pubtypes 00000000 0000000000000000 0000000000000000 >> 00002152 2**0 >> 33 .debug_str 00000069 0000000000000000 0000000000000000 00002166 >> 2**0 >> 34 .debug_ranges 00000000 0000000000000000 0000000000000000 000021d9 >> 2**0 >> $ ./bin/llvm-objdump -h...

...perhaps it does some other things that we don't do, but I haven't seen it) which only emits full definitions of classes in the object file that holds and object’s vtable. -- adrian > >>> - LLDB wants the .apple_XXX accelerator tables, GDB wants >>> .debug_pubnames/.debug_pubtypes >> >> Agreed. >> >>> So it would be great to have a "-debugger" flag that could be specified >>> >>> -debugger=lldb >>> -debugger=gdb >>> >>> Not sure on the option name, but I do like the idea. >> >> We...

Another example would be .debug_pubnames and .debug_pubtypes sections. Currently these default to omitted for Darwin and PS4, but included everywhere else. My initial patch for "tuning" changes the PS4 platform criterion to the SCE debugger predicate; quite likely the "not Darwin" criterion ought to be "not LLDB" or in other w...

...ducing >>> resulting size of >>> binary. >>> >>>    - Build accelerator/index tables. >>>      = .debug_aranges, .debug_names, .gdb_index, >>> .debug_pubnames, >>> .debug_pubtypes. >>> >>>    - Strip unneeded tables. >>>      = .debug_aranges, .debug_names, .gdb_index, >>> .debug_pubnames, >>> .debug_pubtypes. >>> >>>    - Compress or decompress debug...

...o fix this with a smarter implementation). >> >> As far as object file sizes go, in the resulting clang binary (2.3GB), >> the new .debug_names section takes up about 160MB (7%), which isn't >> negligible, but considering that it supersedes the >> .debug_pubnames/.debug_pubtypes tables whose combined size is 490MB >> (21% of the binary), switching to this table (and dropping the other >> two) will have a positive impact on the binary size. Further >> reductions can be made by merging the individual indexes into one >> large index as a part of the...

...n_alignment__) (NOLOAD) : > { > *(.zdebug_aranges) > } > .debug_pubnames BLOCK(__section_alignment__) (NOLOAD) : > { > *(.debug_pubnames) > } > .zdebug_pubnames BLOCK(__section_alignment__) (NOLOAD) : > { > *(.zdebug_pubnames) > } > .debug_pubtypes BLOCK(__section_alignment__) (NOLOAD) : > { > *(.debug_pubtypes) > } > .zdebug_pubtypes BLOCK(__section_alignment__) (NOLOAD) : > { > *(.zdebug_pubtypes) > } > /* DWARF 2. */ > .debug_info BLOCK(__section_alignment__) (NOLOAD) : > { >...

...000020bb > 2**0 > 29 .debug_macinfo 00000000 0000000000000000 0000000000000000 000020cf > 2**0 > 30 .debug_line 00000053 0000000000000000 0000000000000000 000020e3 > 2**0 > 31 .debug_loc 00000000 0000000000000000 0000000000000000 0000213e > 2**0 > 32 .debug_pubtypes 00000000 0000000000000000 0000000000000000 00002152 > 2**0 > 33 .debug_str 00000069 0000000000000000 0000000000000000 00002166 > 2**0 > 34 .debug_ranges 00000000 0000000000000000 0000000000000000 000021d9 > 2**0 > $ ./bin/llvm-objdump -h a.out | grep debug >...

...fo, which isn't a > default setup on linux. I have tried measuring the sizes without that > flag and with fission enabled (-gsplit-dwarf) and the results are: > without compression: > - clang binary: 960 MB > - .debug_names: 130 MB (13%) > - debug_pubnames: 175 MB (18%) > - debug_pubtypes: 204 MB (21%) > - median time for setting a breakpoint on non-existent function > (variance +/- 2%): > real 0m3.526s > user 0m3.156s > sys 0m0.364s > > with -Wl,--compress-debug-sections=zlib: > - clang binary: 440 MB > - .debug_names: 80MB (18%) > - .debug_pubnames...

...en it) > > > > > > > > which only emits full definitions of classes in the object file that holds and object’s vtable. > > -- adrian > > > > >>> - LLDB wants the .apple_XXX accelerator tables, GDB wants > >>> .debug_pubnames/.debug_pubtypes > >> > >> Agreed. > >> > >>> So it would be great to have a "-debugger" flag that could be specified > >>> > >>> -debugger=lldb > >>> -debugger=gdb > >>> > >>> Not sure on the option name,...