This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Patch to simplify reload register allocation
- To: Bernd Schmidt <bernds at cygnus dot co dot uk>
- Subject: Re: Patch to simplify reload register allocation
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Sun, 17 Oct 1999 03:44:32 -0600
- cc: gcc-patches at gcc dot gnu dot org
- Reply-To: law at cygnus dot com
In message <Pine.LNX.4.10.9910171017200.3329-100000@biriani.cygnus.co.uk>you
write:
>
> > [ FWIW, if someone wants to clean up the z8k, I'm more than happy to cont
[ ... ]
>
> I tried to build it yesterday, but it seems to be in a really bad shape.
Yup. We stopped building it regularly at least a year ago, if not earlier.
It only ever had one customer and was always rather fragile. Maybe make it
available as an example of how *not* to write a port :-)
> When should I send an updated patch?
Well there were a couple pieces that I thought we could go ahead and deal
with independently of the revamp. I took care of the easy one tonight
(reload_mode & reload_nregs -> rld[].blah.). But I thought there was at
least one other independent hunk we could/should deal with first.
After that, we'll have to see how much more carnage we get from the GC and
genrecog work. There's also at least 2 more more batch of work to gcse
that is already in the queue (though we've been running it at Cygnus for
nearly a year now, so I'm fairly confident it's not going to hose the world).
There's no reason you can't go ahead and send a new patch after we deal with
the independent stuff -- we can encourage the hard core folks to go ahead and
start beating on it.
jeff