public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: giovannibajo@libero.it
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	kevin@proximity.com.au, nobody@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
Date: Thu, 15 May 2003 10:40:00 -0000	[thread overview]
Message-ID: <20030515104003.23619.qmail@sources.redhat.com> (raw)

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


                 reply	other threads:[~2003-05-15 10:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030515104003.23619.qmail@sources.redhat.com \
    --to=giovannibajo@libero.it \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=kevin@proximity.com.au \
    --cc=nobody@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).