From: Jeffrey A Law <law@hurl.cygnus.com>
To: egcs@cygnus.com
Subject: Re: Reload patch to improve 386 code
Date: Mon, 18 Aug 1997 14:54:49 -0000 [thread overview]
Message-ID: <9708181406.AA23985@issan.informatik.uni-dortmund.de> (raw)
Message-ID: <19970818145449.V27ePIm5lkP0q8zSnLspn2aGRX7azwaFSfujt6eDWRE@z> (raw)
In-Reply-To: Reload patch to improve 386 code
In message <9708181258.AA19853@moene.indiv.nluug.nl>you write:
> Isn't this something that would have been solved [ coniunctivus
> irrealis ! ] by live range splitting ?
Not entirely. live range splitting should significantly reduce
the number of spills, but it won't always be able to completely
eliminate them (in theory it can completely eliminate them, but
in practice it doesn't). Thus you still need to deal with spilling
registers.
Jeff
next reply other threads:[~1997-08-18 14:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-18 14:53 Philippe Laliberte [this message]
1997-08-18 14:53 ` front end interface Andreas Schwab
1997-08-18 14:54 ` Reload patch to improve 386 code Jeffrey A Law
1997-08-18 15:10 ` Will egcs support MachTen? Jeffrey A Law
1997-08-18 15:11 ` double alignment patch for x86 Dave Love
1997-08-18 15:11 ` GCC Projects? Jeffrey A Law
1997-08-18 15:11 Reload patch to improve 386 code meissner
1997-08-18 15:22 ` Monday morning Jeffrey A Law
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=9708181406.AA23985@issan.informatik.uni-dortmund.de \
--to=law@hurl.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).