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 rtl-optimization/50101] [4.5/4.6 regression] GCC 4.5 and 4.6 generate suboptimal code on ppc for countdown loops when the CTR register cannot be used Date: Mon, 02 Jul 2012 12:03:00 -0000 [thread overview] Message-ID: <bug-50101-4-oUXwRiOIUU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-50101-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50101 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|4.5.4 |4.6.4 --- Comment #10 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-07-02 12:02:35 UTC --- The 4.5 branch is being closed, adjusting target milestone.
next prev parent reply other threads:[~2012-07-02 12:03 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-16 20:57 [Bug rtl-optimization/50101] New: " meissner at gcc dot gnu.org 2011-08-16 21:22 ` [Bug rtl-optimization/50101] " meissner at gcc dot gnu.org 2011-08-17 8:13 ` rguenth at gcc dot gnu.org 2011-08-17 15:46 ` meissner at gcc dot gnu.org 2011-08-17 15:47 ` meissner at gcc dot gnu.org 2011-08-17 15:48 ` meissner at gcc dot gnu.org 2011-08-17 16:32 ` meissner at gcc dot gnu.org 2011-08-18 9:01 ` rguenth at gcc dot gnu.org 2011-08-19 14:12 ` meissner at linux dot vnet.ibm.com 2011-08-19 15:54 ` law at redhat dot com 2011-12-15 20:53 ` [Bug rtl-optimization/50101] [4.5/4.6 regression] " pinskia at gcc dot gnu.org 2012-07-02 12:03 ` rguenth at gcc dot gnu.org [this message] 2013-04-12 16:18 ` [Bug rtl-optimization/50101] [4.6 " jakub 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-50101-4-oUXwRiOIUU@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).