This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Add sh4a support to the SH port


On Jul 28, 2004, amylaar@spamcop.net (Joern Rennecke) wrote:

>> FWIW, I'm about to contribute SH2a support, and that brings in the
>> need for at least two new multilibs, and possibly 4 if we refrain from
>> using SH2 libs for -m2a and SH2e for -m2a-single-only.  Comments?

> Please, don't add gratitouisly new multilibs to the sh-elf configuration
> defaults.

That was my thought as well.  Unfortunately, sh2a and sh2a-single
aren't compatible with other SH variants, so they will need separate
multilibs.  sh2a-single-only and sh2a-nofpu can use the same multilibs
as the corresponding sh4 and sh4a variants.

> Note, if you just want to tune for a particular processor, you can use
> the --with-multilib-list configuration option to justomize the multilibs
> that are built.

Yup.  I hope I got it all right :-)

BTW, I noticed that if we disable the -m2 multilib, we get -m2 mapped
to the -m1 ABI (t-sh sequence m1,m2,m3,... implies that, I think).
However, IIRC -m1 and -m2 actually use slightly different ABIs, so it
wouldn't be correct to share them.  Shouldn't we remove `m1,' from
that list?

-- 
Alexandre Oliva             http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]