This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug debug/12500] New: stabs debug info -- void no longer a predefined / builtin type
- From: "taylor at candd dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 3 Oct 2003 15:48:20 -0000
- Subject: [Bug debug/12500] New: stabs debug info -- void no longer a predefined / builtin type
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12500
Summary: stabs debug info -- void no longer a predefined /
builtin type
Product: gcc
Version: 3.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: debug
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: taylor at candd dot org
CC: gcc-bugs at gcc dot gnu dot org
[Observed in i686-pc-linux-gnu native and i686-pc-linux-gnu x powerpc-elf-eabi;
but problem is really configuration independent.]
Pick your favorite .c file, compile it with -gstabs -S, and examine
the output. At the top of the file you will find the stabs entries
for the predefined / builtin data types -- int, char, short, long,
et cetera. In 2.95.3, the list included 'void'; in 3.3.1, void is
absent. This causes subsequent errors in the debug information for
functions and variables that reference void.
The fix is a one liner -- file gcc/dbxout.c, function dbxout_typedefs,
change the line:
&& COMPLETE_TYPE_P (type)
to:
&& COMPLETE_OR_VOID_TYPE_P (type)
With this patch, it bootstraps just fine.
I'm running the testsuite now for i686-pc-linux-gnu native; so far no
regressions.