search for: hash_id

...ted here - https://reviews.llvm.org/P8164. (It still has a questions: whether base types should be put into type table, whether references into type table should be done by DW_AT_signature or just by offset, etc.. ) While handling that separate type table the DWARF aware linker would check the only hash_id and put only one type description with the same id in the final type table. It also would allow us to solve that -flto=thin problem - http://lists.llvm.org/pipermail/llvm-dev/2020-May/141938.html (there is dsymutil example there). i.e., the case when type definition would be removed will not occur...

...t still has a >Alexey> questions: whether base types should be put into type table, whether references into type table >Alexey> should be done by DW_AT_signature or just by offset, etc.. ) While handling that separate type table >Alexey> the DWARF aware linker would check the only hash_id and put only one type description >Alexey> with the same id in the final type table. It also would allow us to solve that -flto=thin problem - >Alexey> http://lists.llvm.org/pipermail/llvm-dev/2020-May/141938.html (there is dsymutil example there). >Alexey> i.e., the case when ty...

...Alexey> questions: whether base types should be put into type table, whether references into type table >> >Alexey> should be done by DW_AT_signature or just by offset, etc.. ) While handling that separate type table >> >Alexey> the DWARF aware linker would check the only hash_id and put only one type description >> >Alexey> with the same id in the final type table. It also would allow us to solve that -flto=thin problem - >> >Alexey> http://lists.llvm.org/pipermail/llvm-dev/2020-May/141938.html (there is dsymutil example there). >> >Alexey...

...types should be put into type table, whether references into type table >>>> >> >Alexey> should be done by DW_AT_signature or just by offset, etc.. ) While handling that separate type table >>>> >> >Alexey> the DWARF aware linker would check the only hash_id and put only one type description >>>> >> >Alexey> with the same id in the final type table. It also would allow us to solve that -flto=thin problem - >>>> >> >Alexey> http://lists.llvm.org/pipermail/llvm-dev/2020-May/141938.html (there is dsymutil e...

...> table, whether references into type table > > >>>> >> >Alexey> should be done by DW_AT_signature or just by offset, > etc.. ) While handling that separate type table > > >>>> >> >Alexey> the DWARF aware linker would check the only hash_id and > put only one type description > > >>>> >> >Alexey> with the same id in the final type table. It also would > allow us to solve that -flto=thin problem - > > >>>> >> >Alexey> > http://lists.llvm.org/pipermail/llvm-dev/2020-Ma...

...ns: whether base types should be put into type table, whether references into type table >> >> >Alexey> should be done by DW_AT_signature or just by offset, etc.. ) While handling that separate type table >> >> >Alexey> the DWARF aware linker would check the only hash_id and put only one type description >> >> >Alexey> with the same id in the final type table. It also would allow us to solve that -flto=thin problem - >> >> >Alexey> http://lists.llvm.org/pipermail/llvm-dev/2020-May/141938.html (there is dsymutil example there). &...

It makes me sad that the linker (via a library or otherwise) has to be "DWARF-aware" to be able to effectively handle --gc-sections, COMDATs, --icf etc for debug info, without leaving large blocks of data kicking around. The patching to -1 (or equivalent) is probably a good lightweight solution (though I'd love it if it could be done based on section type in the future rather than