public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/18628] miscompilation of complex switch statement
Date: Tue, 23 Nov 2004 15:39:00 -0000 [thread overview]
Message-ID: <20041123153932.22273.qmail@sourceware.org> (raw)
In-Reply-To: <20041123151338.18628.micis@gmx.de>
------- Additional Comments From reichelt at gcc dot gnu dot org 2004-11-23 15:39 -------
I can confirm this on i686-pc-linux-gnu just using "-O2".
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |reichelt at gcc dot gnu dot
| |org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18628
next prev parent reply other threads:[~2004-11-23 15:39 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-23 15:13 [Bug tree-optimization/18628] New: " micis at gmx dot de
2004-11-23 15:15 ` [Bug tree-optimization/18628] " micis at gmx dot de
2004-11-23 15:17 ` [Bug middle-end/18628] " pinskia at gcc dot gnu dot org
2004-11-23 15:39 ` reichelt at gcc dot gnu dot org [this message]
2004-11-23 16:11 ` [Bug middle-end/18628] [4.0 regression] " reichelt at gcc dot gnu dot org
2004-11-23 16:16 ` reichelt at gcc dot gnu dot org
2004-11-23 16:34 ` reichelt at gcc dot gnu dot org
2004-11-23 16:53 ` [Bug middle-end/18628] [4.0 regression] miscompilation of switch statement in loop reichelt at gcc dot gnu dot org
2004-11-23 17:09 ` pinskia at gcc dot gnu dot org
2004-11-23 17:13 ` pinskia at gcc dot gnu dot org
2004-11-23 17:22 ` pinskia at gcc dot gnu dot org
2004-11-23 17:38 ` pinskia at gcc dot gnu dot org
2004-11-23 17:49 ` pinskia at gcc dot gnu dot org
2004-11-23 18:15 ` pinskia at gcc dot gnu dot org
2004-11-28 18:02 ` roger at eyesopen dot com
2004-12-15 12:30 ` steven at gcc dot gnu dot org
2004-12-15 13:54 ` steven at gcc dot gnu dot org
2004-12-15 14:11 ` pinskia at gcc dot gnu dot org
2004-12-15 23:52 ` giovannibajo at libero dot it
2004-12-16 7:52 ` micis at gmx dot de
2005-01-05 17:09 ` steven at gcc dot gnu dot org
2005-01-07 10:24 ` reichelt at gcc dot gnu dot org
2005-02-13 18:50 ` neroden at gcc dot gnu dot org
2005-03-09 10:19 ` [Bug middle-end/18628] [4.0/4.1 " aoliva at gcc dot gnu dot org
2005-03-09 10:31 ` aoliva at redhat dot com
2005-03-09 16:14 ` roger at eyesopen dot com
2005-03-10 13:47 ` [Bug rtl-optimization/18628] " rth at gcc dot gnu dot org
2005-03-10 20:38 ` aoliva at redhat dot com
2005-03-10 23:00 ` pluto at pld-linux dot org
2005-03-10 23:13 ` pinskia at gcc dot gnu dot org
2005-03-11 0:52 ` law at redhat dot com
2005-03-11 12:45 ` rth at gcc dot gnu dot org
2005-03-14 20:07 ` cvs-commit at gcc dot gnu dot org
2005-03-14 20:33 ` cvs-commit at gcc dot gnu dot org
2005-03-14 23:43 ` aoliva 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=20041123153932.22273.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: 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).