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 middle-end/17657] [4.0 Regression] ICE in expand_case Date: Wed, 06 Oct 2004 13:12:00 -0000 [thread overview] Message-ID: <20041006131240.5909.qmail@sourceware.org> (raw) In-Reply-To: <20040924161937.17657.jakub@gcc.gnu.org> ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-10-06 13:12 ------- Here is another example except we will not have a cast at all when it comes to expand time: extern signed char foo (int); void bar (void) { signed char tmp = foo (0); int t1 = tmp; switch (t1) { case 1: foo (1); break; case 2: foo (2); break; case 3: foo (3); break; case 4: foo (4); break; case 5: foo (5); break; case 6: foo (6); break; case 7: foo (7); break; case 255: foo (8); break; default: break; } } -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17657
next prev parent reply other threads:[~2004-10-06 13:12 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-09-24 16:19 [Bug c++/17657] New: " jakub at gcc dot gnu dot org 2004-09-24 16:22 ` [Bug c++/17657] " arjanv at redhat dot com 2004-09-24 17:19 ` [Bug middle-end/17657] " pinskia at gcc dot gnu dot org 2004-09-24 17:28 ` [Bug middle-end/17657] [4.0 Regression] " pinskia at gcc dot gnu dot org 2004-10-04 4:07 ` pinskia at gcc dot gnu dot org 2004-10-04 4:15 ` pinskia at gcc dot gnu dot org 2004-10-04 8:43 ` steven at gcc dot gnu dot org 2004-10-06 13:12 ` pinskia at gcc dot gnu dot org [this message] 2004-10-06 13:24 ` stevenb at suse dot de 2004-10-06 13:26 ` pinskia at gcc dot gnu dot org 2004-10-09 18:22 ` pinskia at gcc dot gnu dot org 2004-10-11 3:42 ` cvs-commit at gcc dot gnu dot org 2004-10-11 3:42 ` pinskia at gcc dot gnu dot org 2004-10-11 16:11 ` cvs-commit at gcc dot gnu dot org 2004-10-11 17:02 ` pinskia 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=20041006131240.5909.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).