public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joern Rennecke <amylaar@cygnus.co.uk>
To: egcs@cygnus.com
Subject: Re: Reload patch to improve 386 code
Date: Tue, 19 Aug 1997 19:00:07 -0000	[thread overview]
Message-ID: <199708191800.TAA25100@phal.cygnus.co.uk> (raw)
In-Reply-To: Pine.SOL.3.90.970819095143.291G-100000@starsky.informatik.rwth-aachen.de

> Then, there are some simplifications that could be done. I don't like the
> inheritance code, find_equiv_reg and all that. IMHO reload shouldn't try to be
> very clever about this sort of thing - the reload_cse_regs pass can be made
> more clever. I've already submitted a patch to Kenner that enables
> reload_cse_regs to generate optional reloads. If we could add some more
> cleverness (e.g. deleting redundant stores into spill slots or eliminating
> register-register copies), quite a bit of code in reload could be deleted.
> I've already made some experiments in this direction which indicate that this
> approach may be feasible.

The problem with this is that you might have additional spills if you
remove reload inherits - when you inherit a reload that needs a secondary
reload, you extend the lifetime of only one reload register, instead of needing
two (or more, when a tertiary reload would be needed too.)

Moreover, if you remove reload inherits from / to memory, you might end
up with code that looks like it could have an alias problem for doing cse on
it, and reload_cse can't do anything.

I actually think that the reload inheriting code should be mae smarter.
I did some patches to do that and got more benefit for the code I tested
than from reload_cse.  However, they never got accepted for the FSF gcc...
I'll re-fit them into egcs when I find some time for that.  Should I
sent them as multiple (conflicting) patches or as a single patch?

The main issues are:

- inheriting reloads from non-reload registers

- emitting more complete REG_ notes when doing reloads, so that they can
  be found for inherits

- being smarter about finding possible inherits

> Another way of simplifying reload would be to try to generate auto-inc
> addressing after reload has run, not before. That would eliminate some more
> special-case code (and it might make other parts of the compiler simpler as
> well).

But then you wouldn't get the heuristics for the earlier passes right.

             reply	other threads:[~1997-08-19 19:00 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-08-19 19:00 Joern Rennecke [this message]
     [not found] <Pine.SOL.3.90.970819095143.291G-100000@starsky.informatik.rwth-aachen.de>
1998-09-04  5:03 ` Jeffrey A Law
1998-09-04  5:05   ` Bernd Schmidt
1998-09-04 22:36     ` Joern Rennecke
1998-09-05  4:45     ` Jeffrey A Law
1998-09-05 15:49       ` Joern Rennecke
1998-09-05 15:44         ` Jeffrey A Law
1998-09-06  1:09           ` Mark Mitchell
1998-09-06  1:09             ` Jeffrey A Law
1998-09-07  9:48       ` Bernd Schmidt
1998-09-07 19:09         ` Joern Rennecke
1998-09-07 18:26           ` Jeffrey A Law
1998-09-07 19:09         ` Jeffrey A Law
1998-09-04 21:38   ` Joern Rennecke
1998-09-04 21:38     ` Jeffrey A Law
  -- strict thread matches above, loose matches on Subject: below --
1997-08-21 16:51 Problems on PowerPC David Edelsohn
1997-08-21 17:37 ` Reload patch to improve 386 code Bernd Schmidt
1997-08-21 16:51 Joern Rennecke
1997-08-21 15:20 egcs repository Joel Sherrill
1997-08-21 15:47 ` Reload patch to improve 386 code Bernd Schmidt
1997-08-19  8:50 Jakub Jelinek
1997-08-19  7:36 egcs: A new compiler project to merge the existing GCC forks (fwd) Robert Wilhelm
1997-08-19  8:08 ` Reload patch to improve 386 code Bernd Schmidt
1997-08-19  8:08 ` Bernd Schmidt
1997-08-19  8:08 ` Jeffrey A Law
1997-08-18 20:47 Mike Meissner
1997-08-18 20:46 Joern Rennecke
1997-08-18 18:55 David S. Miller
1997-08-18 19:09 ` Jeffrey A Law
1997-08-18 15:36 Toon Moene
1997-08-18 15:11 meissner
1997-08-18 14:53 meissner
1997-08-18 14:53 Monday morning Philippe Laliberte
1997-08-18 14:54 ` Reload patch to improve 386 code Jeffrey A Law
1997-08-18 14:53 Toon Moene
1997-08-18  8:13 Test result for 970814 on native sparc-sun-solaris2.5.1 Klaus Kaempf
1997-08-18  8:22 ` Reload patch to improve 386 code Bernd Schmidt
1997-08-18 10:11 ` Bernd Schmidt

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=199708191800.TAA25100@phal.cygnus.co.uk \
    --to=amylaar@cygnus.co.uk \
    --cc=egcs@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).