Re: [microblaze-uclinux] General question to everybody using microblaze

[John Williams <jwilliams@xxxxxxxxxxxxxx>]

Hi Richard,

Richard Wicks wrote:
> How many of you have seen your code get stuck (permanently) in __mulsi3?
> 
> I think there is a bug in libgcc.a - I've seen this happen more than once and 
> in multiple operating systems.

Can't say I've ever seen it.  A thought - are you sure that your code is
compiled with the right options, matching the configuration of the CPU?
For example, if your CPU has neither hard MUL or barrel shift, but your
code is compiled and linked expecting the hard shift, then mulsi3 will
attempt to execute invalid opcodes.

In uClinux land it is all handled by auto-config, but you should do a
make clean on your uClinux-dist after changing CPU options like this to
make sure your kernel, libs and apps are compiled with the correct options.

Regards,

John
___________________________
microblaze-uclinux mailing list
microblaze-uclinux@xxxxxxxxxxxxxx
Project Home Page : http://www.itee.uq.edu.au/~jwilliams/mblaze-uclinux
Mailing List Archive : http://www.itee.uq.edu.au/~listarch/microblaze-uclinux/