From: meissner@cygnus.com <meissner@cygnus.com>
To: egcs@cygnus.com
Subject: Re: Reload patch to improve 386 code
Date: Mon, 18 Aug 1997 14:53:46 -0000 [thread overview]
Message-ID: <199708181443.KAA22450@tweedledumb.cygnus.com> (raw)
In-Reply-To: Reload patch to improve 386 code
| > I have come up with a patch for the reload pass that can
| > improve the generated code on the i386 quite dramatically.
| > The problem with reload is that when it decides to spill
| > a hard register, it spills _all_ pseudos allocated to
| > this hard register. This is often not necessary, it is
| > possible to use register life information to determine
| > that certain pseudos are not live across any instructions
| > that need reloads, and thus need not be spilled.
|
| Isn't this something that would have been solved [ coniunctivus
| irrealis ! ] by live range splitting ?
|
| "pseudo's that are not live across instructions" sounds to me as
| the definition of the place to split the liveness range.
|
| Or am I missing something ?
My opinion is reload needs to be rewritten completely. I'm in the middle of
working on a beginning of live range splitting right now, but it probably will
be some time before it moves to egcs (ie, its not ready yet).
| OTOH, "beter een vogel in de hand dan tien in de lucht" (sorry,
| couldn't resist).
|
| Cheers,
| Toon.
|
next reply other threads:[~1997-08-18 14:53 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-18 14:53 meissner [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 ` Jeffrey A Law
1998-09-07 19:09 ` Joern Rennecke
1998-09-07 18:26 ` 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 19:00 Joern Rennecke
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 ` Jeffrey A Law
1997-08-19 8:08 ` Bernd Schmidt
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 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=199708181443.KAA22450@tweedledumb.cygnus.com \
--to=meissner@cygnus.com \
--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).