Hi, On Sat, Dec 14, 2024 at 3:34 AM Masahiro Yamada <masahiroy@xxxxxxxxxx> wrote: > > On Fri, Nov 22, 2024 at 5:43 AM Sami Tolvanen <samitolvanen@xxxxxxxxxx> wrote: > > > > +When a symbol pointer is found in DWARF, gendwarfksyms can use its > > +type for calculating symbol versions even if the symbol is defined > > +elsewhere. The name of the symbol pointer is expected to start with > > +`__gendwarfksyms_ptr_`, followed by the name of the exported symbol. > > I am interested in this sentence. > > __GENDWARFKSYMS_EXPORT() is primarily introduced to handle > EXPORT_SYMBOL() in *.S files. > In fact, .discard.gendwarfksyms is always output for EXPORT_SYMBOL() > from *.c files. > > Can we make it faster by processing only symbol references in the > .dscard.gendwarfksyms section, and skipping all other sections entirely? I don't think we can, because the DWARF type information is still all in the same .debug_info section no matter where we place the actual symbol references. Also, locating exported symbols from the debugging information is already pretty quick, the slow part is actually recursing through the types, which would still be the same amount of work even if we had separate debugging information only for .discard.gendwarfksyms. > > +4.3. Adding structure members > > +============================= > > + > > +Perhaps the most common ABI compatible changeis adding a member to a > > changeis -> change is Thanks, I'll fix this. Sami
