public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/30105] missed code hoisting Date: Thu, 07 Dec 2006 14:20:00 -0000 [thread overview] Message-ID: <20061207142028.21433.qmail@sourceware.org> (raw) In-Reply-To: <bug-30105-1008@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from rguenth at gcc dot gnu dot org 2006-12-07 14:20 ------- Confirmed (but it's not PRE). -- rguenth at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rguenth at gcc dot gnu dot | |org Severity|normal |enhancement Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Keywords| |missed-optimization Last reconfirmed|0000-00-00 00:00:00 |2006-12-07 14:20:28 date| | Summary|missed PRE |missed code hoisting http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30105
next prev parent reply other threads:[~2006-12-07 14:20 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-12-07 6:22 [Bug tree-optimization/30105] New: missed PRE dann at godzilla dot ics dot uci dot edu 2006-12-07 14:20 ` rguenth at gcc dot gnu dot org [this message] 2006-12-07 18:18 ` [Bug tree-optimization/30105] missed PRE (add) pinskia at gcc dot gnu dot org 2006-12-09 6:51 ` [Bug tree-optimization/30105] reassoc can sometimes get in the way of PRE pinskia at gcc dot gnu dot org 2006-12-09 14:40 ` dberlin at gcc dot gnu dot org 2006-12-09 15:06 ` dberlin at gcc dot gnu dot org 2006-12-12 6:07 ` dann at godzilla dot ics dot uci dot edu 2006-12-12 16:49 ` dberlin at dberlin 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=20061207142028.21433.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).