public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/30980] [4.3 Regression] Recent complex miscompilation Date: Fri, 29 Jun 2007 18:00:00 -0000 [thread overview] Message-ID: <20070629180025.31444.qmail@sourceware.org> (raw) In-Reply-To: <bug-30980-133@http.gcc.gnu.org/bugzilla/> ------- Comment #16 from mmitchel at gcc dot gnu dot org 2007-06-29 18:00 ------- This problem is reported fixed; may we close this PR? -- mmitchel at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P3 |P1 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30980
next prev parent reply other threads:[~2007-06-29 18:00 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-02-27 12:39 [Bug c++/30980] New: " pcarlini at suse dot de 2007-02-27 13:21 ` [Bug c++/30980] " pcarlini at suse dot de 2007-02-27 13:27 ` [Bug target/30980] " rguenth at gcc dot gnu dot org 2007-02-27 13:30 ` pcarlini at suse dot de 2007-02-27 13:39 ` pcarlini at suse dot de 2007-02-27 13:41 ` pcarlini at suse dot de 2007-02-27 15:43 ` pinskia at gcc dot gnu dot org 2007-02-27 15:48 ` pinskia at gcc dot gnu dot org 2007-02-27 17:25 ` geoffk at gcc dot gnu dot org 2007-03-11 12:19 ` dominiq at lps dot ens dot fr 2007-03-13 12:57 ` dominiq at lps dot ens dot fr 2007-03-13 13:22 ` rguenth at gcc dot gnu dot org 2007-03-13 13:26 ` rguenth at gcc dot gnu dot org 2007-03-13 14:48 ` dominiq at lps dot ens dot fr 2007-03-17 0:26 ` dominiq at lps dot ens dot fr 2007-03-22 16:22 ` dominiq at lps dot ens dot fr 2007-06-29 18:00 ` mmitchel at gcc dot gnu dot org [this message] 2007-06-29 18:10 ` pcarlini at suse dot de
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=20070629180025.31444.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).