public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/66642] transform_to_exit_first_loop_alt doesn't use result of low iteration count loop Date: Thu, 09 Jul 2015 11:17:00 -0000 [thread overview] Message-ID: <bug-66642-4-XgptAsljrC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66642-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66642 vries at gcc dot gnu.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |FIXED Assignee|unassigned at gcc dot gnu.org |vries at gcc dot gnu.org --- Comment #7 from vries at gcc dot gnu.org --- patch committed, marking resolved-fixed.
prev parent reply other threads:[~2015-07-09 11:17 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-23 15:47 [Bug tree-optimization/66642] New: " vries at gcc dot gnu.org 2015-06-23 15:50 ` [Bug tree-optimization/66642] " vries at gcc dot gnu.org 2015-06-24 14:17 ` vries at gcc dot gnu.org 2015-06-24 14:17 ` vries at gcc dot gnu.org 2015-06-27 5:25 ` vries at gcc dot gnu.org 2015-06-30 9:58 ` vries at gcc dot gnu.org 2015-07-07 16:25 ` vries at gcc dot gnu.org 2015-07-09 11:17 ` vries at gcc dot gnu.org [this message]
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-66642-4-XgptAsljrC@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).