From: David Edelsohn <dje.gcc@gmail.com>
To: Alan Modra <amodra@gmail.com>, Pat Haugen <pthaugen@us.ibm.com>,
gcc-patches@gcc.gnu.org
Subject: Re: [RS6000] Fix PR54131, ICE building 416.gamess
Date: Tue, 31 Jul 2012 14:36:00 -0000 [thread overview]
Message-ID: <CAGWvny=ra8fs7D9jyiGaK-tVAPSWxzaCNVBRBE0HD32uktYbmw@mail.gmail.com> (raw)
In-Reply-To: <20120731115121.GS3182@bubble.grove.modra.org>
On Tue, Jul 31, 2012 at 7:51 AM, Alan Modra <amodra@gmail.com> wrote:
> This cures the 'Y' constraint of being overly restrictive with lo_sum
> offsets. I've added a comment that explains why it is wrong to limit
> the range of lo_sum offsets. Bootstrapped and regressiotn tested
> powerpc-linux. OK to apply?
>
> PR target/54131
> * config/rs6000/rs6000.c (mem_operand_gpr): Don't limit range
> of lo_sum offsets. Comment. Assert mode at least word size
> rather than bypassing powerpc64 word offset check.
Okay.
Thanks, David
prev parent reply other threads:[~2012-07-31 14:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF1B2923F2.E3980D6E-ON86257A4B.00769310-86257A4B.00769C1F@us.ibm.com>
2012-07-31 11:59 ` Alan Modra
2012-07-31 14:36 ` David Edelsohn [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='CAGWvny=ra8fs7D9jyiGaK-tVAPSWxzaCNVBRBE0HD32uktYbmw@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=amodra@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=pthaugen@us.ibm.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).