public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: kevin@proximity.com.au To: gcc-gnats@gcc.gnu.org Subject: c++/10796: gianormous enum values Date: Thu, 15 May 2003 07:26:00 -0000 [thread overview] Message-ID: <20030515072401.12465.qmail@sources.redhat.com> (raw) >Number: 10796 >Category: c++ >Synopsis: gianormous enum values >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-illegal-code >Submitter-Id: net >Arrival-Date: Thu May 15 07:26:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Kevin Cousins >Release: gcc version 3.2.2 >Organization: >Environment: Linux 2.4.18-17.7.x i686 >Description: In C++, according to Stroustrup, enums can grow to sizeof(int). On this machine, sizeof(int)==4, but I when exploring the maximum size enum value g++ would honour, I got an ICE. The following code (put it in a file called enum.C) COMPILES with given command line and runs $ cat enum.C <<EOF enum test { acceptable = 0x7fffffffffffffff, unacceptable = 0xffffffffffffffff }; int main() { test t = acceptable, u = unacceptable; return 0; } EOF $ g++ -save-temps enum.C -o enum $ ./enum >How-To-Repeat: Replace line in enum.C that says: acceptable = 0x7fffffffffffffff, with the following line: acceptable = -1, and attempt to compile with command line as given. >Fix: Don't use ridiculous enum values? Is that sufficient, or should the compiler be able to pick this up? >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2003-05-15 7:26 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=20030515072401.12465.qmail@sources.redhat.com \ --to=kevin@proximity.com.au \ --cc=gcc-gnats@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: linkBe 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).