This is the mail archive of the
mailing list for the GCC project.
Re: make sh-1 support in gcc obsolete?
- From: Joern Rennecke <joern dot rennecke at superh dot com>
- To: Ralf Corsepius <corsepiu at faw dot uni-ulm dot de>
- Cc: GCC List <gcc at gcc dot gnu dot org>, Joel Sherrill <joel dot sherrill at OARcorp dot com>
- Date: Wed, 29 May 2002 13:13:08 +0100
- Subject: Re: make sh-1 support in gcc obsolete?
- Organization: SuperH UK Ltd.
- References: <3CF40F53.54D445D3@superh.com> <1022665471.8970.7647.camel@mccallum>
Ralf Corsepius wrote:
[sh-1 is broken and sh-coff was broken]
> This is sad to hear. I am inclined this qualifies to be a bug in GCC and
> as a regression to gcc-2.95.x
> No, this perspective doesn't match. The SH1/sh-coff is among the targets
> RTEMS supports.
Are there still people using it, apart from testing that it still works?
> RTEMS currently is in the process of switching to 3.1 (Still using
> SH-coff, still supporting the SH1), so we probably will encounter the
> problems you mention.
Note that the assembler silently assembles the file as SH-2 code, and
thus it is linked and run by the simulator as SH-2. But tests on SH1 hardware
can be expected to fail.
If we want to continue to support SH-1, we should have the compiler pass an
option to the assembler to limit the acceptable instruction set to the one
being used, so that regressions are caught. Otherwise, SH-2 instruction are
just too likely to sneak back in.
2430 Aztec West / Almondsbury / BRISTOL / BS32 4AQ
T:+44 1454 462330