This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: c/9100: [3.3/3.4 regression] illegal binary constant causes gcc to seg fault
- From: bangerth at dealii dot org
- To: gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, sander_pool at pobox dot com
- Date: 8 Jan 2003 01:19:50 -0000
- Subject: Re: c/9100: [3.3/3.4 regression] illegal binary constant causes gcc to seg fault
- Reply-to: bangerth at dealii dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, nobody at gcc dot gnu dot org, sander_pool at pobox dot com, gcc-gnats at gcc dot gnu dot org
Old Synopsis: illegal binary constant causes gcc to seg fault
New Synopsis: [3.3/3.4 regression] illegal binary constant causes gcc to seg fault
State-Changed-From-To: open->analyzed
State-Changed-By: bangerth
State-Changed-When: Tue Jan 7 17:19:50 2003
State-Changed-Why:
A minimal testcase is this (just this one line):
-------------------------
int i = (0b11111000 == 0);
-------------------------
It crashes both the C and C++ front ends with a SegFault.
This is a regression from gcc3.2 that happens both on
the 3.3 branch as well as on the mainline. It also happens
on x86-Linux, not only the win-x-avr crosscompiler for which
the report initially was.
W.
The crash for me:
tmp/g> /home/bangerth/bin/gcc-3.3-pre/bin/gcc x.c
x.c:1:9: invalid suffix "b11111000" on integer constant
x.c:1: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9100