From: Eric Botcazou <ebotcazou@adacore.com>
To: gcc-patches@gcc.gnu.org
Cc: Richard Guenther <rguenther@suse.de>,
Jakub Jelinek <jakub@redhat.com>,
"Joseph S. Myers" <joseph@codesourcery.com>
Subject: Re: Fix PR rtl-optimization/52629
Date: Tue, 27 Mar 2012 21:01:00 -0000 [thread overview]
Message-ID: <201203272300.54654.ebotcazou@adacore.com> (raw)
In-Reply-To: <201203261042.13711.ebotcazou@adacore.com>
> Bootstrapped/regtested on x86_64-suse-linux, applied on mainline. Should
> it be applied to the release branches as well?
>
>
> 2012-03-26 Eric Botcazou <ebotcazou@adacore.com>
>
> PR rtl-optimization/52629
> * reload1.c (count_pseudo): Short-circuit common case.
> (count_spilled_pseudo): Return early for pseudos without hard regs.
> Assert that the pseudo has got a hard reg before manipulating it.
RMs, what's your decision?
--
Eric Botcazou
next prev parent reply other threads:[~2012-03-27 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-26 8:42 Eric Botcazou
2012-03-27 21:01 ` Eric Botcazou [this message]
2012-03-28 8:06 ` Richard Guenther
2012-03-28 9:17 ` Eric Botcazou
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=201203272300.54654.ebotcazou@adacore.com \
--to=ebotcazou@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=rguenther@suse.de \
/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).