From: Steven Bosscher <stevenb.gcc@gmail.com>
To: Steven Bosscher <stevenb.gcc@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Ian Lance Taylor <iant@google.com>,
rdsandiford@googlemail.com
Subject: Re: [patch] Split parts of cse_insn out to a few new functions
Date: Mon, 26 Mar 2012 19:13:00 -0000 [thread overview]
Message-ID: <CABu31nP9VTnaOb89vP7H4Q8C3Zssaq8BwjwvyDu1yZg2uk-9rw@mail.gmail.com> (raw)
In-Reply-To: <87mx736v9q.fsf@talisman.home>
On Mon, Mar 26, 2012 at 9:02 PM, Richard Sandiford
<rdsandiford@googlemail.com> wrote:
>> * cse.c (cse_canonicalized_basic_blocks): New simple bitmap to
>> tag basic blocks that have already been traversed at least once,
>> so that all insns have been canonicalized.
>> (cse_insn): Call canonicalize_insn only if the basic block that
>> contains insn is visited for the first time.
>> (cse_extended_basic_block): After visiting all insns in a basic
>> block, mark the block in cse_canonicalized_basic_blocks.
>> (cse_main): Setup and destroy cse_canonicalized_basic_blocks.
>
> OK, thanks (without the microoptimisation, as you say).
Thanks, will commit!
> Out of curiosity, do you still see this bit as useful:
>
> /* We potentially will process this insn many times. Therefore,
> drop the REG_EQUAL note if it is equal to the SET_SRC of the
> unique set in INSN.
>
> Do not do so if the REG_EQUAL note is for a STRICT_LOW_PART,
> because cse_insn handles those specially. */
>
> ? Does "many times" mean in CSE, or later?
It means "in CSE", yes. But with the patch to canonicalize only once,
I suppose this can go away again.
Having said that, I do believe it would be good if we avoid having
REG_EQUAL notes that are rtx_equal_p to the SET_SRC. This happens
quite frequently after CSE. I'm not sure how to clean them up.
Ciao!
Steven
prev parent reply other threads:[~2012-03-26 19:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-20 21:07 Steven Bosscher
2012-03-21 0:14 ` Ian Lance Taylor
2012-03-21 23:10 ` Steven Bosscher
2012-03-21 23:15 ` Steven Bosscher
2012-03-26 19:02 ` Richard Sandiford
2012-03-26 19:13 ` Steven Bosscher [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=CABu31nP9VTnaOb89vP7H4Q8C3Zssaq8BwjwvyDu1yZg2uk-9rw@mail.gmail.com \
--to=stevenb.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iant@google.com \
--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).