[fpc-devel] What is the status of -CfLIBGCC ? Can ib be considered good/working for embedded targets?

[Florian Klämpfl]

Am 14.02.21 um 14:08 schrieb Michael Ring via fpc-devel:
> I am having a lot of (no-)fun with floating point on Cortex-M0, current 
> summary would be to say that things get pretty unreliable once I start 
> using Floats.
> 
> I today stumbled over -CfLIBGCC, sounds interesting, but compiling 
> cross-compiler trunk with this option ends up in an error:
> 
> 
> /Library/Developer/CommandLineTools/usr/bin/make -C embedded all
> /Users/ring/fpcupdeluxe-embedded/fpc/bin/x86_64-darwin/ppcarm -Cparmv6m 
> -Ur -Tembedded -Parm -XParm-none-eabi- -Ur -Xs -O2 -n -Fi../inc 
> -Fi../arm -FD/Users/ring/fpcupdeluxe-embedded/fpc/bin/x86_64-darwin -FE. 
> -FU/Users/ring/devel/freepascal/rtl/units/arm-embedded 
> -vw-n-h-l-d-u-t-p-c- -ap 
> -Fl/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk/usr/lib -darm 
> -dRELEASE -O1 -g -Cflibgcc  -Us -Sg system.pp @system.cfg
> system.inc(426,5) Fatal: Internal error 200312126
> Fatal: Compilation aborted
> 
> Is the option worth asking for a fix so that it compiles again or is it 
> anyway so experimental that I better try to find the issues within softfp?

libgcc was never really usable on any target. softfpu works very well on 
most targets, so it is most likely a simple armv6m issue. I propose we 
hunt the armv6m issue down, it is probably just a simple cg issue which 
surfaces by the softfloat code.