This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/46655] invalid '.line 0' directive emitted with -g
- From: "dje at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Mon, 29 Nov 2010 22:28:30 +0000
- Subject: [Bug target/46655] invalid '.line 0' directive emitted with -g
- Auto-submitted: auto-generated
- References: <bug-46655-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46655
--- Comment #9 from David Edelsohn <dje at gcc dot gnu.org> 2010-11-29 22:28:20 UTC ---
If I understand correctly, the line 0 error occurs in both AIX and BFD, so it
is not a bug. Did something change in GCC that now generates line 0 debug
information?
Is the 64K limit really new? Is this really a change in AIX as or did
something else change and start generating files referencing line numbers
larger than 64K?
I believe the line number field in XCOFF is defined in /usr/include/linenum.h.
According to that file, in 32 bit mode, line numbers are represented by an
unsigned short, whose maximum value is 65535. In 64 bit mode, line numbers are
represented by unsigned int.
I have not seen this error while bootstrapping GCC on AIX. The error looks
correct. What else changed?