This is the mail archive of the
mailing list for the GCC project.
Re: Add little/big endian multilib variants to mips*-rtems*
Richard Sandiford wrote:
Ralf Corsepius <email@example.com> writes:Does there need to be a special error catcher for mips*el-rtems so it
can't be configured?
On Fri, 2006-06-09 at 10:18 +0100, Richard Sandiford wrote:
Ralf Corsepius <firstname.lastname@example.org> writes:Depends on what you mean.
It adds little/big endian multilib variants to mips*-rtems* targets.What about mips*el-rtems? Is that not a support configuration?
This patch has been in use for the official RTEMS toolchains for a while
and should not have any influence on any other targets.
-MULTILIB_OPTIONS = mips1/mips3/mips32 msoft-float/msingle-float
-MULTILIB_DIRNAMES = mips1 mips3 mips32 soft-float single
-MULTILIB_MATCHES = msingle-float=m4650
+# default is mips1 EB hard-float
Little "endian mips" is supported, but a separate mips*el-rtems target
tuple is not supported.
I meant the latter. It's just that, whether supported or not, I think
the configuration _is_ accepted. The *el handling is done separately
in config.gcc, for all MIPS targets.
If you're happy with mips*el-rtems silently doing something strange,
the patch is OK.