public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Adam Nemet <anemet@caviumnetworks.com>
To: Ian Lance Taylor <iant@google.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: PATCH COMMITTED: Permit splitters to create new pseudo regs in combine
Date: Thu, 26 Jul 2007 07:49:00 -0000	[thread overview]
Message-ID: <87k5sniyo5.fsf@localhost.localdomain.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <m3sl7cc8a3.fsf@localhost.localdomain> (Ian Lance Taylor's message of "25 Jul 2007 17:34:28 -0700")

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?

Adam

  reply	other threads:[~2007-07-26  4:20 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 [this message]
2007-08-02  1:43   ` Ian Lance Taylor
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=87k5sniyo5.fsf@localhost.localdomain.i-did-not-set--mail-host-address--so-tickle-me \
    --to=anemet@caviumnetworks.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=iant@google.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).