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 optimization/12863] [3.4/3.5 regression] basic block reordering fails for fallthru of casesi Date: Mon, 09 Feb 2004 05:04:00 -0000 [thread overview] Message-ID: <20040209050430.29283.qmail@sources.redhat.com> (raw) In-Reply-To: <20031031212321.12863.danglin@gcc.gnu.org> ------- Additional Comments From pinskia at gcc dot gnu dot org 2004-02-09 05:04 ------- So the build problem is gone but this is still a regression. -- What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |NEW Last reconfirmed|2004-01-10 20:27:24 |2004-02-09 05:04:27 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12863
next prev parent reply other threads:[~2004-02-09 5:04 UTC|newest] Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-10-31 21:31 [Bug optimization/12863] New: [3.4 " danglin at gcc dot gnu dot org 2003-10-31 22:14 ` [Bug optimization/12863] " pinskia at gcc dot gnu dot org 2003-11-01 1:16 ` jh at suse dot cz 2003-11-01 1:52 ` danglin at gcc dot gnu dot org 2003-11-02 22:50 ` pinskia at gcc dot gnu dot org 2003-12-29 17:44 ` pinskia at gcc dot gnu dot org 2004-01-10 11:30 ` steven at gcc dot gnu dot org 2004-01-10 17:53 ` dave at hiauly1 dot hia dot nrc dot ca 2004-01-10 20:27 ` pinskia at gcc dot gnu dot org 2004-01-10 20:54 ` dave at hiauly1 dot hia dot nrc dot ca 2004-01-11 0:27 ` pinskia at gcc dot gnu dot org 2004-01-12 16:32 ` cvs-commit at gcc dot gnu dot org 2004-01-12 17:27 ` pinskia at gcc dot gnu dot org 2004-01-12 18:50 ` dave at hiauly1 dot hia dot nrc dot ca 2004-01-27 13:11 ` [Bug optimization/12863] [3.4/3.5 " cvs-commit at gcc dot gnu dot org 2004-01-29 3:34 ` dhazeghi at yahoo dot com 2004-02-09 2:46 ` dave at hiauly1 dot hia dot nrc dot ca 2004-02-09 5:04 ` pinskia at gcc dot gnu dot org [this message] 2004-03-09 20:44 ` mmitchel at gcc dot gnu dot org 2004-03-21 8:36 ` zlomek at gcc dot gnu dot org 2004-03-27 0:03 ` dave at hiauly1 dot hia dot nrc dot ca 2004-05-29 17:58 ` [Bug rtl-optimization/12863] " mmitchel at gcc dot gnu dot org 2004-08-19 20:32 ` mmitchel at gcc dot gnu dot org 2004-09-27 3:44 ` [Bug rtl-optimization/12863] [3.4/4.0 " pinskia at gcc dot gnu dot org 2004-10-31 2:04 ` mmitchel at gcc dot gnu dot org 2004-12-05 3:26 ` [Bug rtl-optimization/12863] [3.4 " pinskia at gcc dot gnu dot org 2004-12-05 3:48 ` dave at hiauly1 dot hia dot nrc dot ca 2005-05-19 17:24 ` mmitchel 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=20040209050430.29283.qmail@sources.redhat.com \ --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).