From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23662 invoked by alias); 15 May 2003 10:40:03 -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 23643 invoked by uid 48); 15 May 2003 10:40:03 -0000 Date: Thu, 15 May 2003 10:40:00 -0000 Message-ID: <20030515104003.23619.qmail@sources.redhat.com> To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, kevin@proximity.com.au, nobody@gcc.gnu.org From: giovannibajo@libero.it Reply-To: giovannibajo@libero.it, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, kevin@proximity.com.au, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: c++/10796: [3.3/3.4 regression] ICE (segfault) when defining an enum with two values: -1 and MAX_INT_64BIT X-SW-Source: 2003-05/txt/msg01781.txt.bz2 List-Id: Old Synopsis: gianormous enum values New Synopsis: [3.3/3.4 regression] ICE (segfault) when defining an enum with two values: -1 and MAX_INT_64BIT State-Changed-From-To: open->analyzed State-Changed-By: bajo State-Changed-When: Thu May 15 10:40:02 2003 State-Changed-Why: Confirmed. To make it clearer, the following code snippet ICEs GCC: ------------------------------------------------ enum test { one = -1, two = 0xffffffffffffffff }; ------------------------------------------------ pr10796.cpp:4: error: integer constant is too large for "long" type pr10796.cpp:5: internal compiler error: Segmentation fault Please submit a full bug report, I call the code legal because it would be possible to use "unsigned long long" as underlying type for such an enumerator (at least on x86, where its size is 8 bytes), even if I don't know what the C++ ABI says about this. Anyway, we shouldn't segfault on this for sure. It's a regression wrt 2.95 (which was failing gracefully). http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10796