From: Olivier Hainque <hainque@adacore.com>
To: Richard Sandiford <rdsandiford@googlemail.com>
Cc: Olivier Hainque <hainque@adacore.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: strengthen protection against REG_EQUIV/EQUAL on !REG set
Date: Thu, 26 Apr 2012 08:39:00 -0000 [thread overview]
Message-ID: <AB04221B-8C3B-490C-B22A-996C6881DDF4@adacore.com> (raw)
In-Reply-To: <871unc7pkb.fsf@talisman.home>
Hello Richard,
On Apr 25, 2012, at 00:06 , Richard Sandiford wrote:
> STRICT_LOW_PART is OK too.
Ah, right.
> Would be nice to use a single function that knows about the extra
> contraints here. Maybe something like the attached?
>
> I'm deliberately requiring the SET to the first rtx in the PARALLEL.
Looks cleaner indeed. Do you want me to test ?
Thanks a lot for your feedback.
Olivier
next prev parent reply other threads:[~2012-04-26 8:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-12 9:54 Olivier Hainque
2012-04-12 10:02 ` Olivier Hainque
2012-04-24 22:06 ` Richard Sandiford
2012-04-26 8:39 ` Olivier Hainque [this message]
2012-05-04 13:34 ` Olivier Hainque
2012-05-04 14:16 ` Richard Sandiford
2012-05-04 15:44 ` Olivier Hainque
2012-05-07 9:36 ` Richard Sandiford
2014-05-26 12:28 Olivier Hainque
2014-05-27 18:23 ` Jeff Law
2014-05-28 8:42 ` Olivier Hainque
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=AB04221B-8C3B-490C-B22A-996C6881DDF4@adacore.com \
--to=hainque@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rdsandiford@googlemail.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).