This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/49202] MMIX: Wrong debugging information generated (UNKNOWN: length 2)
- From: "hp at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 16 Aug 2011 01:27:06 +0000
- Subject: [Bug target/49202] MMIX: Wrong debugging information generated (UNKNOWN: length 2)
- Auto-submitted: auto-generated
- References: <bug-49202-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49202
Hans-Peter Nilsson <hp at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution| |INVALID
--- Comment #4 from Hans-Peter Nilsson <hp at gcc dot gnu.org> 2011-08-16 01:27:06 UTC ---
(In reply to comment #3)
> If you have very old binutils/gdb, you might want to use -gstrict-dwarf, then
> gcc won't emit the various debug info extensions, including discriminators.
I can confirm that this happens with HEAD binutils of today.
I'm going to close this PR as "invalid" because formally the description
trivially points to being a binutils bug rather than a gcc bug. I'm also going
to open a binutils bug and crossref this PR. Later on maybe reopen this PR if
there's a gcc bug too.