public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/20008] [4.0 Regression] internal compiler error: in expand_case, at stmt.c:2397 Date: Wed, 16 Feb 2005 23:36:00 -0000 [thread overview] Message-ID: <20050216191659.22773.qmail@sourceware.org> (raw) In-Reply-To: <20050216162007.20008.caolanm@redhat.com> ------- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-16 19:16 ------- Reduced testcase: typedef enum _SECStatus { SECWouldBlock = -2, SECFailure = -1, SECSuccess = 0 } SECStatus; typedef enum { SEC_ERROR_BAD_SIGNATURE = (-0x2000) + 10 } SECErrorCodes; void g(void); void f(SECStatus status) { switch( status ) { case SEC_ERROR_BAD_SIGNATURE : g(); break ; } } : Search converges between 2004-10-25-161001-trunk (#610) and 2004-10-26-161001-trunk (#611). This is undefined code (as SEC_ERROR_BAD_SIGNATURE is out of the range of SECStatus). Enums are defined differently in C++ than C. -- What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Component|middle-end |c++ Ever Confirmed| |1 Last reconfirmed|0000-00-00 00:00:00 |2005-02-16 19:16:58 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20008
next prev parent reply other threads:[~2005-02-16 19:17 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-02-16 19:46 [Bug c++/20008] New: " caolanm at redhat dot com 2005-02-16 19:47 ` [Bug c++/20008] " caolanm at redhat dot com 2005-02-16 19:56 ` [Bug c++/20008] [4.0 Regression] " pinskia at gcc dot gnu dot org 2005-02-16 22:03 ` [Bug middle-end/20008] " pinskia at gcc dot gnu dot org 2005-02-16 23:36 ` pinskia at gcc dot gnu dot org [this message] 2005-02-17 15:47 ` [Bug c++/20008] " caolanm at redhat dot com 2005-02-17 20:00 ` aoliva at gcc dot gnu dot org 2005-02-17 20:27 ` aoliva at redhat dot com 2005-02-18 18:29 ` cvs-commit at gcc dot gnu dot org 2005-02-18 18:32 ` jakub at gcc dot gnu dot org
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=20050216191659.22773.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).