Re: Building RedBoot for SH3 targets with new toolchain

[Jonathan Larmour <jifl@eCosCentric.com>]

John Dallaway wrote:
> Hi Jifl
> 
> There is a problem linking RedBoot for all SH3 targets with the new
> sh-elf toolchain based on GCC 4.3.2. For example, linking RAM RedBoot
> for sh7708:
> 
>> /var/local/releng/build/redboot/install/lib/extras.o: In function `fis_write':
[snip]
> Building RedBoot for target sh4_202_md (an SH4 target) works fine with
> the new tools and building RedBoot for SH3 targets works fine with the
> old tools.
> 
> Any idea what's going wrong here?

gcc's lib1funcs.asm has that function surrounded by:
#elif defined (__SH3__) || defined (__SH3E__) || defined (__SH4__) ||
defined (__SH4_SINGLE__) || defined (__SH4_SINGLE_ONLY__) || defined
(__SH4_NOFPU__)
/* This code used shld, thus is not suitable for SH1 / SH2.  */

So it's not built in an sh2 multilib. Therefore we will need to build an
sh3 multilib. Bummer. It needs to be added at line 2286 of config.gcc. I'm
rebuilding for linux now, so you can try it out when that's done and I've
packaged it up, but you may want to add this to any todo list you've got to
be sure it's tracked. If that build is ok, I'll have the grief of trying to
rebuild the cygwin version.

Jifl
-- 
eCosCentric Limited      http://www.eCosCentric.com/     The eCos experts
Barnwell House, Barnwell Drive, Cambridge, UK.       Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.
------["Si fractum non sit, noli id reficere"]------       Opinions==mine