public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/47033] loop distribution has problems on sane testcases Date: Wed, 29 Dec 2010 16:13:00 -0000 [thread overview] Message-ID: <bug-47033-4-LUA9dfOVvx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-47033-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47033 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |missed-optimization Status|UNCONFIRMED |NEW Last reconfirmed| |2010.12.29 16:12:57 Ever Confirmed|0 |1 --- Comment #3 from Richard Guenther <rguenth at gcc dot gnu.org> 2010-12-29 16:12:57 UTC --- Loop distribution shouldn't fail if loop header copying was applied and it would be nice to know why it does.
next prev parent reply other threads:[~2010-12-29 16:13 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-12-21 19:19 [Bug middle-end/47033] New: " hubicka at gcc dot gnu.org 2010-12-28 16:11 ` [Bug middle-end/47033] " rguenth at gcc dot gnu.org 2010-12-29 5:15 ` spop at gcc dot gnu.org 2010-12-29 16:13 ` rguenth at gcc dot gnu.org [this message] 2011-01-01 13:30 ` hubicka at ucw dot cz 2021-12-26 12:35 ` pinskia at gcc dot gnu.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=bug-47033-4-LUA9dfOVvx@http.gcc.gnu.org/bugzilla/ \ --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).