This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Sparc bogosity
- From: George dot R dot Goffe at seagate dot com
- To: robertlipe at usa dot net
- Cc: gcc at gcc dot gnu dot org
- Date: Thu, 31 Jan 2002 15:09:33 -0800
- Subject: Re: Sparc bogosity
Howdy,
I have some spare cycles (sometimes more than others) but if you can let me
know what you want to do and maybe how to do it, I have Lots of sparcv9
systems to play with.
Regards,
George...
Robert Lipe <robertlipe@usa.net>@gcc.gnu.org on 01/31/2002 02:49:05 PM
Sent by: gcc-owner@gcc.gnu.org
To: gcc@gcc.gnu.org
cc:
Subject: Re: Sparc bogosity
Geoff Keating wrote:
> lucier@math.purdue.edu writes:
>
> > when the sparcv9 port is broken ...
>
> ... no-one notices, because few people have sparcv9 hardware, fast
> sparcv9 hardware is expensive, and there is no sparcv9 simulator.
> Probably the greatest possible contribution to the stability of the
> sparcv9 port would be to write a simulator for it.
Or for someone with appropriate hardware and OS to set up a cron job to
bootstrap and nag about it, just like Geoff's thingy for PPC. Sure, a
simulator would be nice becuase then "anyone" could debug the failure.
Someone that cares about SparcV9 just needs to find the clock cycles
to do the bootstrap and test thing and a little bit of time to help pick
through the results, work with the "offender", test pending patches, and
such. It doesn't need to be a compiler jock to do this; someone with
hardware access, dilligence, and reasonable problem solving skills could
make a difference.
RJL