> On 8/2/21 9:04 PM, Lee Noar wrote:
>> Unfortunately, GCC 10 does not support module generation as yet which
>> is why GCC 4 is still our main compiler.
>> The problem is that libscl which is the interface to the
>> SharedCLibrary and what modules are linked against needs to be built
>> as hard-float+FPA, however, FPA code generation was removed from GCC
>> some years ago and is no longer supported.
>
> I've not been following the developments the last years but I seem to
> (vaguely) remember that all floating point related SharedCLibrary calls
> were optional in the stub code so that in non-FPA capable multilib
> versions of the build those calls were simple not available. So a, say,
> strcpy() was supported, but sin() not. After all floating point using
> module code is/was quite rare.
ISTR that FPA floating point couldn't be used in modules, something to
do with modules running in SVC mode and FPA instructions being emulated.
I think VFP is OK though.
>> Really, what we need is a SharedCLibrary that supports VFP.
>
> And probably also as EABI flavour, not APCS, ie. get rid of the chunked
> stack which isn't even used so in SVC mode.
That may be difficult to get implemented in the DDE C compiler! But, yes
that would mean that APCS-32 support wouldn't have to be added to GCC 10
just to support modules.
Lee.
_______________________________________________
GCCSDK mailing list gcc@gccsdk.riscos.info
Bugzilla: http://www.riscos.info/bugzilla/index.cgi
List Info: http://www.riscos.info/mailman/listinfo/gcc
Main Page: http://www.riscos.info/index.php/GCCSDK
No comments:
Post a Comment