public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Vladimir Makarov <vmakarov@redhat.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: RFA: patch for PR48455
Date: Wed, 13 Apr 2011 17:12:00 -0000	[thread overview]
Message-ID: <4DA5D98F.7060806@redhat.com> (raw)
In-Reply-To: <4DA5D8B3.2080003@redhat.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 04/13/11 11:09, Vladimir Makarov wrote:
> The following patch should improve code size which degradation for arm
> is reported on
> 
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48455
> 
> Is it ok to commit?  The patch was successfully bootstrapped on x86-64
> and i686 with H.J.'s autotester options.
> 
> 2011-04-13  Vladimir Makarov <vmakarov@redhat.com>
> 
>         PR rtl-optimization/48455
>         * ira-costs.c (find_costs_and_classes): Use i_mem_cost instead of
>         `temp_costs->mem_cost'.
OK.
jeff
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNpdmPAAoJEBRtltQi2kC78cUIAKd41H7LfANsVOH5tuY/ZmR9
X7aRad0exevCKhRYuGBfKtZHJ1OHCvOTHxOr6Xvak/BUNuMkuZPaazc5c4rg1HRc
Fo43AM+NuxLHvNWi+gvN4sY1fhrGjYquwu5TNQ7TM26Njvbb1s1JwQtUEdly02yg
HDwSqxqurAfkAD3xrE2+sOUF/WfbE4DFS/OKCqCLr8AnQPXYu8dqA3QRjqoSuBcB
3sd0x/gTplMaJUk/B+B8xrxlOSZSooRCYp3SQhsvEWTUdhNCAYrrh2HDC26H4H9P
Uusc8PHnolU0JL5onwN/mGqu2+mrgJ8Z4Xbc2cSAMnOlf6ATQhpdcTvFUeFA7Rw=
=cfcO
-----END PGP SIGNATURE-----

      reply	other threads:[~2011-04-13 17:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-13 17:09 Vladimir Makarov
2011-04-13 17:12 ` Jeff Law [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=4DA5D98F.7060806@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=vmakarov@redhat.com \
    /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).