public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/50557] [4.7 Regression] Register pressure increase after reassociation (x86, 32 bits)
Date: Wed, 07 Dec 2011 04:02:00 -0000 [thread overview]
Message-ID: <bug-50557-4-Xju226p9oI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50557-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=50557
--- Comment #10 from Andrew Pinski <pinskia at gcc dot gnu.org> 2011-12-07 04:01:36 UTC ---
(In reply to comment #9)
> There is still the old loop re-rolling pass from the rtlopt-branch. I am not
> sure if there were any good reasons for not including it in GCC.
Maybe re-rolling could be pushed up to the tree level where it might catch a
few more things.
next prev parent reply other threads:[~2011-12-07 4:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 11:08 [Bug tree-optimization/50557] New: " izamyatin at gmail dot com
2011-09-28 11:51 ` [Bug tree-optimization/50557] " rguenth at gcc dot gnu.org
2011-09-28 12:17 ` izamyatin at gmail dot com
2011-09-28 12:27 ` wschmidt at gcc dot gnu.org
2011-09-29 9:32 ` izamyatin at gmail dot com
2011-09-29 12:25 ` wschmidt at gcc dot gnu.org
2011-09-30 14:52 ` wschmidt at gcc dot gnu.org
2011-10-07 10:34 ` izamyatin at gmail dot com
2011-10-10 12:40 ` wschmidt at gcc dot gnu.org
2011-10-27 10:30 ` [Bug rtl-optimization/50557] " rguenth at gcc dot gnu.org
2011-12-05 10:46 ` steven at gcc dot gnu.org
2011-12-07 4:02 ` pinskia at gcc dot gnu.org [this message]
2012-01-19 12:52 ` rguenth at gcc dot gnu.org
2012-02-27 10:35 ` rguenth at gcc dot gnu.org
2012-03-22 9:23 ` [Bug rtl-optimization/50557] [4.7/4.8 " rguenth at gcc dot gnu.org
2012-06-14 8:41 ` rguenth at gcc dot gnu.org
2012-09-20 10:24 ` jakub at gcc dot gnu.org
2012-10-04 11:17 ` izamyatin at gmail dot com
2013-01-01 5:26 ` [Bug rtl-optimization/50557] [4.7 " pinskia at gcc dot gnu.org
2013-04-11 7:59 ` rguenth at gcc dot gnu.org
2014-06-12 13:02 ` rguenth 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-50557-4-Xju226p9oI@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: link
Be 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).