public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/52543] lower-subreg.c: code bloat of 300%-400% for multi-word memory splits
Date: Thu, 03 May 2012 17:51:00 -0000	[thread overview]
Message-ID: <bug-52543-4-l3NUaCrYy5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52543-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52543

--- Comment #8 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> 2012-05-03 17:50:20 UTC ---
lower-subreg patched committed here:

http://gcc.gnu.org/ml/gcc-cvs/2012-05/msg00011.html


  parent reply	other threads:[~2012-05-03 17:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09 15:39 [Bug rtl-optimization/52543] New: lower-subreg.c: code bloat of 300%-400% for bulti-word " gjl at gcc dot gnu.org
2012-03-09 15:39 ` [Bug rtl-optimization/52543] " gjl at gcc dot gnu.org
2012-03-09 15:41 ` gjl at gcc dot gnu.org
2012-03-09 15:45 ` gjl at gcc dot gnu.org
2012-03-09 15:47 ` gjl at gcc dot gnu.org
2012-03-21 13:26 ` [Bug rtl-optimization/52543] lower-subreg.c: code bloat of 300%-400% for multi-word " gjl at gcc dot gnu.org
2012-03-22 15:13 ` gjl at gcc dot gnu.org
2012-03-22 16:08 ` gjl at gcc dot gnu.org
2012-05-03 17:05 ` rsandifo at gcc dot gnu.org
2012-05-03 17:51 ` rsandifo at gcc dot gnu.org [this message]
2012-06-27  9:24 ` pinskia at gcc dot gnu.org
2012-08-02 18:30 ` gjl at gcc dot gnu.org
2012-08-02 18:37 ` gjl at gcc dot gnu.org
2012-08-02 18:39 ` gjl at gcc dot gnu.org
2012-09-06 14:38 ` olegendo at gcc dot gnu.org
2012-09-06 22:14 ` olegendo at gcc dot gnu.org
2012-09-15  6:07 ` pinskia at gcc dot gnu.org
2012-09-28  8:21 ` gjl 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-52543-4-l3NUaCrYy5@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).