Go to file
Giulio Benetti 5d4f338234 Revert "configs/olimex_a20_olinuxino_lime2: use NEON+VFPv4 as FPU strategy"
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 f8528acdfd.

Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
(cherry picked from commit 869fe1fbab)
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-09-16 23:45:03 +02:00
arch arch/Config.in.riscv: lp64f ABI is only supported if MMU is enabled 2022-08-29 22:12:43 +02:00
board board/qemu/ppc-bamboo: use path to vmlinux image for copy and paste users 2022-06-07 11:40:53 +02:00
boot package/syslinux: disable documentation 2022-09-16 10:52:07 +02:00
configs Revert "configs/olimex_a20_olinuxino_lime2: use NEON+VFPv4 as FPU strategy" 2022-09-16 23:45:03 +02:00
docs docs/manual/prerequisite.txt: add diffutils 2022-08-29 13:11:42 +02:00
fs fs/oci: entrypoint and command are space-separated lists 2022-05-29 10:33:32 +02:00
linux linux/linux: fix firmware-imx dependency 2022-09-15 10:40:58 +02:00
package package/qoriq-cadence-dp-firmware: fix license info 2022-09-16 16:11:27 +02:00
support support/scripts: fix TABs/spaces in check-host-rpath 2022-09-13 16:38:59 +02:00
system system/skeleton: provide run/lock directory 2022-01-12 20:38:09 +01:00
toolchain toolchain/Config.in: update gcc bug 99410 2022-09-13 16:11:36 +02:00
utils utils/readme.txt: Fix typo "get-developers" 2022-08-14 21:20:35 +02:00
.clang-format .clang-format: initial import from Linux 5.15.6 2022-01-01 15:01:13 +01:00
.defconfig
.flake8 Revert ".flake8: fix check for 80/132 columns" 2021-01-02 17:38:20 +01:00
.gitignore
.gitlab-ci.yml utils/checkpackagelib/lib_sysv: run shellcheck 2022-02-06 18:27:03 +01:00
.shellcheckrc utils/check-package: improve shellcheck reproducibility 2022-08-18 07:59:26 +02:00
CHANGES Update for 2022.02.5 2022-08-31 22:08:58 +02:00
Config.in support/download: Add SFTP support 2022-01-06 09:34:05 +01:00
Config.in.legacy Config.in.legacy: add missing select 2022-09-16 12:18:20 +02:00
COPYING
DEVELOPERS DEVELOPERS: remove useless whitespaces before tabs 2022-09-13 16:43:18 +02:00
Makefile Makefile: enhance reporting error about empty VARS 2022-09-14 11:37:05 +02:00
Makefile.legacy
README docs: move the IRC channel away from Freenode 2021-05-29 22:16:23 +02:00

Buildroot is a simple, efficient and easy-to-use tool to generate embedded
Linux systems through cross-compilation.

The documentation can be found in docs/manual. You can generate a text
document with 'make manual-text' and read output/docs/manual/manual.text.
Online documentation can be found at http://buildroot.org/docs.html

To build and use the buildroot stuff, do the following:

1) run 'make menuconfig'
2) select the target architecture and the packages you wish to compile
3) run 'make'
4) wait while it compiles
5) find the kernel, bootloader, root filesystem, etc. in output/images

You do not need to be root to build or run buildroot.  Have fun!

Buildroot comes with a basic configuration for a number of boards. Run
'make list-defconfigs' to view the list of provided configurations.

Please feed suggestions, bug reports, insults, and bribes back to the
buildroot mailing list: buildroot@buildroot.org
You can also find us on #buildroot on OFTC IRC.

If you would like to contribute patches, please read
https://buildroot.org/manual.html#submitting-patches