From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22721 invoked by alias); 8 Jan 2003 06:46:04 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 22700 invoked by uid 71); 8 Jan 2003 06:46:03 -0000 Date: Wed, 08 Jan 2003 06:46:00 -0000 Message-ID: <20030108064603.22699.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: Neil Booth Subject: Re: c/9100: [3.3/3.4 regression] illegal binary constant causes gcc to seg fault Reply-To: Neil Booth X-SW-Source: 2003-01/txt/msg00523.txt.bz2 List-Id: The following reply was made to PR c/9100; it has been noted by GNATS. From: Neil Booth 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.