This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/20682] New: lost parser
- From: "igodard at pacbell dot net" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 29 Mar 2005 11:35:29 -0000
- Subject: [Bug c++/20682] New: lost parser
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
The attachments are a pair of compiler output/source code runs. The "good" ones
compile OK; the "bad" ones report errors. The difference? One blank line of
whitespace. And the reported errors are in a function about ten functions below
where the whitespace change is. Use diff to see where - it's in the second
function named "equate(".
I've seen a lot of bugs in gcc, but I don't think I've ever seen one that
depended on whitespace :-)
Ivan
--
Summary: lost parser
Product: gcc
Version: 3.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: c++
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: igodard at pacbell dot net
CC: gcc-bugs at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20682