public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu>
To: Daniel Berlin <dberlin@dberlin.org>
Cc: dnovillo@redhat.com, gcc-patches@gcc.gnu.org, amacleod@redhat.com
Subject: Re: [PATCH]: Implement must-def kill operand
Date: Wed, 20 Oct 2004 22:23:00 -0000	[thread overview]
Message-ID: <3CE2FCAE-22E6-11D9-8879-000A95D692F4@physics.uc.edu> (raw)
In-Reply-To: <Pine.LNX.4.60.0410172146490.5720@dberlin.org>


On Oct 17, 2004, at 10:00 PM, Daniel Berlin wrote:

> [Diego, if this isn't accepted for mainline, i'd still like to put it 
> on TCB, so if you could take a look at it, i'd appreciate it]
>
> This large but mostly mechnanical patch implements a RHS for must-defs 
> so that we know what they are killing.
> These operands are renamed just like any other ssa operand.
> This is necessary for sinking type optimizations (including store 
> motion) to work properly in a safe and  efficient manner.
> In particular, it fixes PR 17133

I would like this to go in rather soon because not only fixes a bug
but it also allows us to stabilize part of the aliasing of the
infrastructure.

-- Pinski

  parent reply	other threads:[~2004-10-20 22:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-18  2:29 Daniel Berlin
2004-10-20 17:41 ` Diego Novillo
2004-10-20 17:56   ` Daniel Berlin
2004-10-20 18:08     ` Diego Novillo
2004-10-20 18:28       ` Daniel Berlin
2004-10-20 20:36         ` Diego Novillo
2004-10-20 20:49           ` Daniel Berlin
2004-10-20 20:57             ` Diego Novillo
2004-10-20 21:01               ` Daniel Berlin
     [not found]               ` <531813B6-22DA-11D9-B310-000D93B1B044@dberlin.org>
2004-10-20 21:04                 ` Diego Novillo
2004-10-20 21:27                   ` Daniel Berlin
2004-10-20 22:23 ` Andrew Pinski [this message]
2004-10-23  5:02   ` Mark Mitchell
2004-10-23 12:56     ` Diego Novillo

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=3CE2FCAE-22E6-11D9-8879-000A95D692F4@physics.uc.edu \
    --to=pinskia@physics.uc.edu \
    --cc=amacleod@redhat.com \
    --cc=dberlin@dberlin.org \
    --cc=dnovillo@redhat.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).