From: Eric Botcazou <ebotcazou@adacore.com>
To: Sandra Loosemore <sandra@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, Chung-Lin Tang <cltang@codesourcery.com>
Subject: Re: [patch] fix regrename pass to ensure renamings produce valid insns
Date: Thu, 18 Jun 2015 18:26:00 -0000 [thread overview]
Message-ID: <1919634.FPIRa5rfyH@polaris> (raw)
In-Reply-To: <5581AA41.7010201@codesourcery.com>
> The attached patch teaches regrename to validate insns affected by each
> register renaming before making the change. I can see at least two
> other ways to handle this -- earlier, by rejecting renamings that result
> in invalid instructions when it's searching for the best renaming; or
> later, by validating the entire set of renamings as a group instead of
> incrementally for each one -- but doing it all in regname_do_replace
> seems least disruptive and risky in terms of the existing code.
OK, but the patch looks incomplete, rename_chains should be adjusted as well,
i.e. regrename_do_replace should now return a boolean.
--
Eric Botcazou
next prev parent reply other threads:[~2015-06-18 17:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-17 17:36 Sandra Loosemore
2015-06-17 19:23 ` Richard Sandiford
2015-06-18 18:26 ` Eric Botcazou [this message]
2015-06-24 3:31 ` Sandra Loosemore
2015-06-24 7:59 ` Ramana Radhakrishnan
2015-06-24 14:57 ` Sandra Loosemore
2015-06-24 16:50 ` Eric Botcazou
2015-06-24 16:59 ` Eric Botcazou
2015-06-25 3:53 ` Jeff Law
2015-06-25 12:30 ` Bernd Schmidt
2015-06-25 13:54 ` Eric Botcazou
2015-06-25 13:59 ` Bernd Schmidt
2015-06-29 0:18 ` Sandra Loosemore
2015-06-30 3:54 ` Kito Cheng
2015-06-30 5:08 ` Sandra Loosemore
2015-06-30 5:26 ` Chung-Lin Tang
2015-06-30 6:11 ` Chung-Lin Tang
2015-06-30 9:08 ` Eric Botcazou
2015-06-30 11:03 ` Chung-Lin Tang
2015-06-30 19:11 ` Sandra Loosemore
2015-06-30 21:31 ` Eric Botcazou
2015-07-01 17:03 ` Jeff Law
2015-11-06 10:48 ` Bernd Schmidt
2015-11-06 19:51 ` Jeff Law
2015-11-13 15:13 ` Bernd Schmidt
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=1919634.FPIRa5rfyH@polaris \
--to=ebotcazou@adacore.com \
--cc=cltang@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=sandra@codesourcery.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).