public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joern Rennecke <amylaar@cygnus.co.uk>
To: law@cygnus.com
Cc: rth@cygnus.com, dje@watson.ibm.com,
	Franz.Sirl-kernel@lauterbach.com, egcs@cygnus.com
Subject: Re: stabilization issues ppc-linux
Date: Sun, 31 Jan 1999 23:58:00 -0000	[thread overview]
Message-ID: <199901121550.PAA26878@phal.cygnus.co.uk> (raw)
In-Reply-To: <23767.916133476@hurl.cygnus.com>

> One might argue that it should treat CONSTANT_P_RTX like ADDRESSOF -- delay
> committal until after CSE has finished.  Or even later.  Unlike ADDRESSOF
> gcse could expose more constants via global constant propagation.

It should be OK to commit to the result one when this can be determined -
this can allow to remove some dependent code.
There should also be a cse and jump pass after we commit to values for
CONSTANT_P_RTX.
So maybe we should do this after gcse, just before the the folowing jump
optimizer - but the replacement of CONSTANT_P_RTX itself must not depend on
flag_gcse, of course.

  reply	other threads:[~1999-01-31 23:58 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-31 23:58 Jeffrey A Law
1999-01-31 23:58 ` Franz Sirl
1999-01-31 23:58   ` David Edelsohn
1999-01-31 23:58     ` Jeffrey A Law
1999-01-31 23:58       ` Richard Henderson
1999-01-31 23:58         ` Franz Sirl
1999-01-31 23:58           ` Jeffrey A Law
1999-01-31 23:58         ` Jeffrey A Law
1999-01-31 23:58           ` Joern Rennecke [this message]
1999-01-31 23:58         ` David Edelsohn
1999-01-31 23:58           ` Richard Henderson
1999-01-31 23:58             ` David Edelsohn

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=199901121550.PAA26878@phal.cygnus.co.uk \
    --to=amylaar@cygnus.co.uk \
    --cc=Franz.Sirl-kernel@lauterbach.com \
    --cc=dje@watson.ibm.com \
    --cc=egcs@cygnus.com \
    --cc=law@cygnus.com \
    --cc=rth@cygnus.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).