Re: c/9100: [3.3/3.4 regression] illegal binary constant causes gcc to seg fault

Re: c/9100: [3.3/3.4 regression] illegal binary constant causes gcc to seg fault

[ebotcazou]

Synopsis: [3.3/3.4 regression] illegal binary constant causes gcc to seg fault

State-Changed-From-To: analyzed->closed
State-Changed-By: ebotcazou
State-Changed-When: Tue Feb 11 22:57:09 2003
State-Changed-Why:
    Fixed.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9100

Re: c/9100: [3.3/3.4 regression] illegal binary constant causes gcc to seg fault

[ebotcazou]

Synopsis: [3.3/3.4 regression] illegal binary constant causes gcc to seg fault

Responsible-Changed-From-To: unassigned->ebotcazou
Responsible-Changed-By: ebotcazou
Responsible-Changed-When: Sat Feb  8 16:43:59 2003
Responsible-Changed-Why:
    Working on a fix.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=9100

Re: c/9100: [3.3/3.4 regression] illegal binary constant causes gcc to seg fault

[Neil Booth]

The following reply was made to PR c/9100; it has been noted by GNATS.

From: Neil Booth <neil@daikokuya.co.uk>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	nobody@gcc.gnu.org, sander_pool@pobox.com, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c/9100: [3.3/3.4 regression] illegal binary constant causes gcc to seg fault
Date: Wed, 8 Jan 2003 06:39:28 +0000

 bangerth@dealii.org wrote:-
 
 > 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.
 
 I'd guess this is an unchecked for "error_mark_node" (death to them), and
 quite easy to fix.
 
 Neil.

Re: c/9100: [3.3/3.4 regression] illegal binary constant causes gcc to seg fault

[bangerth]

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