>From the integer multiplication functions (which I rewrote to support the HW 
>32 bit multiplier and 64bit hardware multiplication) I know that the calling 
>conventions for these functions were NOT following the normal 
mspgcc calling conventions, for increased performance.
If this is true for the floating point functions too, it's possible that moving 
the code into a 'normal' compilation unit will break this mechanism.

These functions were declared weak, so any other instance inside the project 
will replace them without error.


----- Ursprüngliche Nachricht -----
Von: Diane Gagne
An: [email protected]
Gesendet am: 09 Jun 2010 23:35:56
Betreff: [Mspgcc-users] Help with floating point multiplication

I am trying to make a faster version of the floating point multiplier.  When
I look at the .lst source of a test function calling floating point
multiplication it calls the function __mulsf3.  When I copy the code from
the file mulsf.c into a separate function of mine it does not tell me when
the answer is overflow anymore.  From this, I think there must be another
function called __mulsf3 that I do not see.   I was wondering where that
function was in the files, or else how the overflow was seen when using the
float multiplication.

I am using a Linux computer with the makefile in the packaging directory to
build the compiler.
_______________________________________________
Mspgcc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users



Reply via email to