public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zack@codesourcery.com>
To: Richard Henderson <rth@redhat.com>,
	Zack Weinberg <zack@codesourcery.com>,
	gcc-patches@gcc.gnu.org
Subject: Re: patch/RFC: PR optimization/8423
Date: Wed, 06 Nov 2002 15:01:00 -0000	[thread overview]
Message-ID: <20021106230116.GA16220@egil.codesourcery.com> (raw)
In-Reply-To: <20021106223345.GI22215@redhat.com>

On Wed, Nov 06, 2002 at 02:33:45PM -0800, Richard Henderson wrote:
> On Wed, Nov 06, 2002 at 11:36:44AM -0800, Zack Weinberg wrote:
> > What actually happens is it blows up compiling libgcc, due to some
> > construct or other that simplify-rtx.c doesn't know how to handle but
> > cse's simplifiers do.  I haven't yet dug into this.
> 
> I should have remembered this.  cse1 is needed so that we
> propagate addressof into memories.  Addressof elimination
> needs to happen before gcse because gcse can't handle 
> aliasing memory and registers.
> 
> So we can neither get rid of cse1 nor move gcse before it.

This is unfortunate.  How hard would it be to teach gcse about aliasing
memory and registers?  I really like the idea of getting rid of a CSE pass.

zw

  reply	other threads:[~2002-11-06 23:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-05 13:55 Zack Weinberg
2002-11-06 11:23 ` Richard Henderson
2002-11-06 11:33   ` Diego Novillo
2002-11-06 14:34     ` Richard Henderson
2002-11-06 11:36   ` Zack Weinberg
2002-11-06 14:33     ` Richard Henderson
2002-11-06 15:01       ` Zack Weinberg [this message]
2002-11-06 15:07         ` Richard Henderson
2002-11-07  3:06       ` Michael Matz
2002-11-05 16:17 Roger Sayle

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=20021106230116.GA16220@egil.codesourcery.com \
    --to=zack@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=rth@redhat.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).