This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

maybe_suppress_debug_info


maybe_suppress_debug_info() is used in C++ to suppress debugging information
generation for C++ classes (as an optimization). note_debug_info_needed() is
used to enable it again, but all note_debug_info_needed() calls are inside #if 0 code.
This causes GCC to miss debugging information for virtual C++ classes
(at least in stabs).


Now comments in code is somewhat confusing. It says it is _slightly_ useful for BINCL,
but we are dropping info in this case. Comment also say that it is not useful with DWARF.


I am thinking of not using maybe_suppress_debug_info() with stabs format when BINCLs are
used, to get all debugging information for virtual C++ classes.


thoughts ?

Thanks,
-Devang


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]