[Buildroot] [PATCH 2/4] Revert "configs/olimex_a20_olinuxino_lime2: use NEON+VFPv4 as FPU strategy"

[Peter Korsgaard]

>>>>> "Giulio" == Giulio Benetti <giulio.benetti at benettiengineering.com> writes:

 > The gcc man page states that specifying Neon as part of the fpu setting
 > has no effect, unless the -funsafe-math-optimizations is also specified,
 > because Neon is not compliant with IEEE 754:
 > ```
 >     If the selected floating-point hardware includes the NEON extension
 >     (e.g. -mfpu=neon), note that floating-point operations are not
 >     generated by GCC's auto-vectorization pass unless
 >     -funsafe-math-optimizations is also specified. This is because NEON
 >     hardware does not fully implement the IEEE 754 standard for
 >     floating-point arithmetic (in particular denormal values are treated
 >     as zero), so the use of NEON instructions may lead to a loss of
 >     precision.
 > ```

 > -funsafe-math-optimizations must be explictly specified per package to
 > really use NEON as FPU, but it's something that is left to the user as
 > well as setting BR2_ARM_FPU_NEON_VFPV4. This way the default
 > BR2_ARM_FPU_VFPV4D16 is used as previously. So let's revert the
 > offending patch.

 > This reverts commit f8528acdfda278ea9f2f9bc8a47eb77ace0c050f.

 > Signed-off-by: Giulio Benetti <giulio.benetti at benettiengineering.com>

Committed to 2022.05.x and 2022.02.x, thanks.

-- 
Bye, Peter Korsgaard