search for: debug_types_table

...is the specific case and is not used inside subprograms usually, then probably it is possible to avoid it. For the same CU - there could probably be cases when references could be ignored: https://reviews.llvm.org/P8165 > > 2. Create additional section - global types table > (.debug_types_table). That would significantly reduce the number > of references inside .debug_info section. It also makes it > possible to have a 4-byte reference in this section instead of > 8-bytes reference into type unit (DW_FORM_ref_types instead of > DW_FORM_ref_sig8). It also makes...

...probably wouldn't be ideal in the compiler & > wouldn't save the debug info linker from having to haev code to handle > the case where it wasn't only used from that subprogram anyway. > >> 2. Create additional section - global types table >> (.debug_types_table). That would significantly reduce the >> number of references inside .debug_info section. It also >> makes it possible to have a 4-byte reference in this section >> instead of 8-bytes reference into type unit >> (DW_FORM_ref_types instead of D...

...t;>>>>>>>>> I will shortly describe the idea of making DWARF be easier processed by dsymutil/DWARFLinker: >>>>>>>>>> >>>>>>>>>> The idea is to have only one "type table" per object file(special section .debug_types_table). >>>>>>>>>> This "type table" would contain all types. >>>>>>>>>> There could be a special type of reference - type_offset - that offset points into the type table. >>>>>>>>>> Basic types could alwa...

...other parts of .debug_info section. That would simplify splitting and removing subprograms out in that sense that it would minimize the number of references that should be parsed and followed. (DW_FORM_ref_subroutine instead of DW_FORM_ref_*, ?) 2. Create additional section - global types table (.debug_types_table). That would significantly reduce the number of references inside .debug_info section. It also makes it possible to have a 4-byte reference in this section instead of 8-bytes reference into type unit (DW_FORM_ref_types instead of DW_FORM_ref_sig8). It also makes it possible to place base types into...

...t;>>>>> I will shortly describe the idea of making DWARF be easier processed by dsymutil/DWARFLinker: >>>>>>>>>>>> >>>>>>>>>>>> The idea is to have only one "type table" per object file(special section .debug_types_table). >>>>>>>>>>>> This "type table" would contain all types. >>>>>>>>>>>> There could be a special type of reference - type_offset - that offset points into the type table. >>>>>>>>>>>&gt...

...gt; >> >> >> >> >> I will shortly describe the idea of making DWARF be easier processed by dsymutil/DWARFLinker: >> >> >> >> >> >> >> >> The idea is to have only one "type table" per object file(special section .debug_types_table). >> >> >> >> This "type table" would contain all types. >> >> >> >> There could be a special type of reference - type_offset - that offset points into the type table. >> >> >> >> Basic types could always be placed in...

...y describe the idea of making DWARF be > easier processed by dsymutil/DWARFLinker: > >>>>>>>>>>>> > >>>>>>>>>>>> The idea is to have only one "type table" per object > file(special section .debug_types_table). > >>>>>>>>>>>> This "type table" would contain all types. > >>>>>>>>>>>> There could be a special type of reference - > type_offset - that offset points into the type table. > >>&gt...

...dea of making DWARF be easier >>> processed by dsymutil/DWARFLinker: >>> >>>>>>>>>>>> >>> >>>>>>>>>>>> The idea is to have only one "type table" per object >>> file(special section .debug_types_table). >>> >>>>>>>>>>>> This "type table" would contain all types. >>> >>>>>>>>>>>> There could be a special type of reference - type_offset - >>> that offset points into the type table. >>...

...cutable it should work with non-fragmented DWARF). That idea is for the tool which works the same way as dsymutil ODR. I will shortly describe the idea of making DWARF be easier processed by dsymutil/DWARFLinker: The idea is to have only one "type table" per object file(special section .debug_types_table). This "type table" would contain all types. There could be a special type of reference - type_offset - that offset points into the type table. Basic types could always be placed into the start of "type table" thus, offsets to basic types most often would be 1 byte. There also...

...DWARF). >> That idea is for the tool which works the same way as dsymutil ODR. >> >> I will shortly describe the idea of making DWARF be easier processed by dsymutil/DWARFLinker: >> >> The idea is to have only one "type table" per object file(special section .debug_types_table). >> This "type table" would contain all types. >> There could be a special type of reference - type_offset - that offset points into the type table. >> Basic types could always be placed into the start of "type table" thus, offsets to basic types >> most...

...e tool which works the same way as dsymutil ODR. >> >> >> >> I will shortly describe the idea of making DWARF be easier processed by dsymutil/DWARFLinker: >> >> >> >> The idea is to have only one "type table" per object file(special section .debug_types_table). >> >> This "type table" would contain all types. >> >> There could be a special type of reference - type_offset - that offset points into the type table. >> >> Basic types could always be placed into the start of "type table" thus, offsets t...

...symutil ODR. >> >> >> >> >> >> I will shortly describe the idea of making DWARF be easier processed by dsymutil/DWARFLinker: >> >> >> >> >> >> The idea is to have only one "type table" per object file(special section .debug_types_table). >> >> >> This "type table" would contain all types. >> >> >> There could be a special type of reference - type_offset - that offset points into the type table. >> >> >> Basic types could always be placed into the start of "type...

...tly describe the idea of making DWARF be easier processed by dsymutil/DWARFLinker: >>>> >>>>>>>>>>>> >>>> >>>>>>>>>>>> The idea is to have only one "type table" per object file(special section .debug_types_table). >>>> >>>>>>>>>>>> This "type table" would contain all types. >>>> >>>>>>>>>>>> There could be a special type of reference - type_offset - that offset points into the type table. >>>&...

...as dsymutil ODR. >>>> >> >>>> >> I will shortly describe the idea of making DWARF be easier processed by dsymutil/DWARFLinker: >>>> >> >>>> >> The idea is to have only one "type table" per object file(special section .debug_types_table). >>>> >> This "type table" would contain all types. >>>> >> There could be a special type of reference - type_offset - that offset points into the type table. >>>> >> Basic types could always be placed into the start of "type tab...

...t; > > >>>> >> I will shortly describe the idea of making DWARF be easier > processed by dsymutil/DWARFLinker: > > >>>> >> > > >>>> >> The idea is to have only one "type table" per object > file(special section .debug_types_table). > > >>>> >> This "type table" would contain all types. > > >>>> >> There could be a special type of reference - type_offset - that > offset points into the type table. > > >>>> >> Basic types could always be plac...

>DWARF was designed in an era when COMDAT and ICF were not a thing, or at least not common, >certainly not when talking about function code. The overhead of a unit occurred only once per >translation unit, so that expense was reasonably amortized. >Splitting functions into their own object-file sections and making them excludable is an evolution of >compiler/linker technology that