This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: schedule_block
- To: law at cygnus dot com
- Subject: Re: schedule_block
- From: Michael Hayes <m dot hayes at elec dot canterbury dot ac dot nz>
- Date: Tue, 15 Dec 1998 23:19:24 +1300 (NZDT)
- Cc: Michael Hayes <m dot hayes at elec dot canterbury dot ac dot nz>, meissner at cygnus dot com, egcs at cygnus dot com
- References: <"13942.9379.994325.687846"@ongaonga.elec.canterbury.ac.nz><22890.913713627@hurl.cygnus.com>
Jeffrey A Law writes:
> It would take a while to dig up the testcases, but after making 3
> attempts to fix all the problems this stupidity introduced I deemed
> it not worth the effort in general.
So what is the proper way to achieve the effect that this piece of
code was trying to do? A rewrite of the register allocator?
The reason I raised this query is that I'm seeing loops that have a
pressing need for a hard register which the register allocator cannot
satisfy, since the register is used for an incoming argument
(even though it may be immediately assigned to another register before
the loop and not used thereafter).
Michael.