This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: A bug in GCC 2.95.2 for SPARC
- To: James dot Cheng at eng dot sun dot com
- Subject: Re: A bug in GCC 2.95.2 for SPARC
- From: "Martin v. Loewis" <martin at loewis dot home dot cs dot tu-berlin dot de>
- Date: Wed, 10 May 2000 23:07:58 +0200
- CC: aoliva at cygnus dot com, gcc-bugs at gcc dot gnu dot org, james dot cheng at eng dot sun dot com
- References: <200005101919.MAA12410@solarcell.Eng.Sun.COM>
> Thanks for your quick reply. However, I do need to use ultrasparc
> instructions.
That makes me curious. Can you please explain why you need that? I'd
think a typical C program would not care about the processor it runs
on...
> I am wondering if you have a timetable for a better support of
> ultrasparc. Is there any way I can track this bug, such as a bug id
> number?
No, there typically is no timetable for features in GCC, please also
look at
http://gcc.gnu.org/cgi-bin/fom.cgi?file=12
To track this bug yourself, you don't need an id number :-) To see
whether it has been already solved, please try a GCC 2.96 snapshot.
If it still exists, feel free to enter a bug report using the gccbug
script of gcc 2.96.
Regards,
Martin