public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: Adam Nemet <anemet@caviumnetworks.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: PATCH COMMITTED: Permit splitters to create new pseudo regs in combine
Date: Thu, 02 Aug 2007 01:43:00 -0000	[thread overview]
Message-ID: <m3zm1aemqy.fsf@localhost.localdomain> (raw)
In-Reply-To: <87k5sniyo5.fsf@localhost.localdomain.i-did-not-set--mail-host-address--so-tickle-me>

Adam Nemet <anemet@caviumnetworks.com> writes:

> Ian Lance Taylor <iant@google.com> writes:
> > I have committed this patch to fix the problem.  This simply changes
> > reg_stat to be a VEC, and grows the VEC when a splitter creates a new
> > pseudo.
> 
> I must be missing something.  Who updates the old-style dataflow
> information that combine uses for the new pseudos created?
> 
> For example in try_combine, don't we now call record_value_for_reg on
> the pseudo that was originally offered by combine instead of the one
> the backend picked?

Sorry, I missed this note earlier.

When we call record_value_for_reg in try_combine, it is resetting the
value recorded for the register to a value set in an earlier insn,
which is correct.

Nothing records the values for the new registers created by the
splitters.  That is OK, as no other insns refer to them.  It is
theoretically possible that this could cause a missed optimization if
the insns generated by a splitter can themselves be combined.  But
that is a rather unlikely scenario, as nobody would write a splitter
that way.

Ian

  reply	other threads:[~2007-08-02  1:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-26  2:58 Ian Lance Taylor
2007-07-26  7:49 ` Adam Nemet
2007-08-02  1:43   ` Ian Lance Taylor [this message]
2007-08-08 21:44     ` Adam Nemet
2007-08-08 23:53       ` Ian Lance Taylor

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=m3zm1aemqy.fsf@localhost.localdomain \
    --to=iant@google.com \
    --cc=anemet@caviumnetworks.com \
    --cc=gcc-patches@gcc.gnu.org \
    /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).