----- Ursprüngliche Nachricht -----
Von: Peter Bigot
Gesendet am: 30 Dez 1899 00:00:00
> Well, it's in stdlib as opposed to being in binutils or gcc. And has
> nothing to do with hardware multiply being used in the demonstration
> program. A one-line program calling printf with a format parameter shows
> the problem.
Okay, than you narrowed it down to the source.
Actually you're the only one who could do that :)
> Which is that when msp430-libc builds the multi-lib variants, it doesn't
> bother to tell the compiler which MCU class to use when building functions
> (it does for the chip-specific crt0 modules, but not for the libc archives
> that supposedly provide family-specific variants). This falls under the
> heading of "how did it ever work", the answer appears to be that it didn't.
> The necessary distinguishing flags were not preserved when mspgcc3's two
> variants (with/without hardware multiply) were converted to multilibs in
> support of mspgcc4's six variants.
Only six variants?
Bascially, ld shouldn't use a lib variant with hardware multiply when the
project parameters tell the compiler not to use hardware multiply for the
project files.
Ar at least there should be an obvious way to tell ld to do so.
Of course linking a lib version with hwmpy when the cpu has no MPY unit is a
no-go, but if it has and hte use don't want it to be used (for whatver reason),
this should be obeyed too.
And then there is the mpy16/mpy32 problem. The libs of course should use the
better version if possible - not only if the global hwmul functions are used
but also if the mpy unit is used directly (if ever, that is).
Different version of the hwmul functions in th egcclib are also necessary (or
are they already there? mspgcc3 only used the mpy16)
> I'll get a new msp430-libc release out later today.
You're a real workaholic.
Thanks for all your work (even if I don't use mspgcc4 as it isn't ready for
critical production environment)
JMGross
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Mspgcc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
