search for: sig8

...he shorter reference might be inadequate) I don't think >> David>the indirection through the type hash is /super/ significant to the >> David>cost - I think it's more in the duplication of many DIEs especially >> David>for function definitions (since the type unit sig8 system only >> David>provides a way to reference the type - not its member functions, their >> David>parameters, etc - so all those DIEs get duplicated in any CU that >> David>needs to provide a definition of a member function). We could >> David>prototype cross-...

...ery David>far away, so the shorter reference might be inadequate) I don't think David>the indirection through the type hash is /super/ significant to the David>cost - I think it's more in the duplication of many DIEs especially David>for function definitions (since the type unit sig8 system only David>provides a way to reference the type - not its member functions, their David>parameters, etc - so all those DIEs get duplicated in any CU that David>needs to provide a definition of a member function). We could David>prototype cross-unit DIE references to lower the cos...

...be inadequate) I don't think >> >> David>the indirection through the type hash is /super/ significant to the >> >> David>cost - I think it's more in the duplication of many DIEs especially >> >> David>for function definitions (since the type unit sig8 system only >> >> David>provides a way to reference the type - not its member functions, their >> >> David>parameters, etc - so all those DIEs get duplicated in any CU that >> >> David>needs to provide a definition of a member function). We could >&gt...

...;t think >>>> >> David>the indirection through the type hash is /super/ significant to the >>>> >> David>cost - I think it's more in the duplication of many DIEs especially >>>> >> David>for function definitions (since the type unit sig8 system only >>>> >> David>provides a way to reference the type - not its member functions, their >>>> >> David>parameters, etc - so all those DIEs get duplicated in any CU that >>>> >> David>needs to provide a definition of a member fun...

...> David>the indirection through the type hash is /super/ > significant to the > > >>>> >> David>cost - I think it's more in the duplication of many DIEs > especially > > >>>> >> David>for function definitions (since the type unit sig8 system > only > > >>>> >> David>provides a way to reference the type - not its member > functions, their > > >>>> >> David>parameters, etc - so all those DIEs get duplicated in any > CU that > > >>>> >> David>...

...t;> 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 would be a special kind of reference - reference inside the type. >> >> >> >> Type units sig8 system - would not be used to reference types. >> >> >> >> >> >> >> >> Types deduplication is assumed to be done, not by linker mechanism for COMDAT, >> >> >> >> but by a tool like dsymutil. This tool would create resulting .de...

...ic types could always be placed into the start of "type table" thus, offsets to basic types >>>>>>>>>> most often would be 1 byte. There also would be a special kind of reference - reference inside the type. >>>>>>>>>> Type units sig8 system - would not be used to reference types. >>>>>>>>>> >>>>>>>>>> Types deduplication is assumed to be done, not by linker mechanism for COMDAT, >>>>>>>>>> but by a tool like dsymutil. This tool would creat...

...t;> >> >> 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 would be a special kind of reference - reference inside the type. >> >> >> Type units sig8 system - would not be used to reference types. >> >> >> >> >> >> Types deduplication is assumed to be done, not by linker mechanism for COMDAT, >> >> >> but by a tool like dsymutil. This tool would create resulting .debug_types_table by putting...

...lways be placed into the start of "type table" thus, offsets to basic types >>>>>>>>>>>> most often would be 1 byte. There also would be a special kind of reference - reference inside the type. >>>>>>>>>>>> Type units sig8 system - would not be used to reference types. >>>>>>>>>>>> >>>>>>>>>>>> Types deduplication is assumed to be done, not by linker mechanism for COMDAT, >>>>>>>>>>>> but by a tool like dsymuti...

...t; "type table" thus, offsets to basic types > >>>>>>>>>>>> most often would be 1 byte. There also would be a > special kind of reference - reference inside the type. > >>>>>>>>>>>> Type units sig8 system - would not be used to > reference types. > >>>>>>>>>>>> > >>>>>>>>>>>> Types deduplication is assumed to be done, not by > linker mechanism for COMDAT, > >>>>>>>&g...

...;> table" thus, offsets to basic types >>> >>>>>>>>>>>> most often would be 1 byte. There also would be a special >>> kind of reference - reference inside the type. >>> >>>>>>>>>>>> Type units sig8 system - would not be used to reference >>> types. >>> >>>>>>>>>>>> >>> >>>>>>>>>>>> Types deduplication is assumed to be done, not by linker >>> mechanism for COMDAT, >>> >>&g...

..."type table" thus, offsets to basic types >>>> >>>>>>>>>>>> most often would be 1 byte. There also would be a special kind of reference - reference inside the type. >>>> >>>>>>>>>>>> Type units sig8 system - would not be used to reference types. >>>> >>>>>>>>>>>> >>>> >>>>>>>>>>>> Types deduplication is assumed to be done, not by linker mechanism for COMDAT, >>>> >>>>>>...

>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