d8dc5315eb
wolfssl contains some assembly code and its configure.ac script enables the assembly code depending on the CPU architecture. However, the detection logic is not sufficient and leads to using the assembly code in situation where it should not. Here are two examples: - As soon as the architecture is mips64/mips64el, it uses assembly code, but that assembly code is not mips64r6 compatible. - As soon as the architecture is RISC-V, it uses assembly code, but that assembly code uses multiplication instructions, without paying attention that the "M" extension may not be available in the RISC-V CPU instruction set. In order to avoid this, we introduce a BR2_PACKAGE_WOLFSSL_ASM_SUPPORTS hidden boolean to decide when to enable/disable assembly code. We set an initial value with the supported CPU architectures, with the exclusion of the problematic cases described above. It is pretty likely that this variable will need tuning progressively, as it is difficult to determine which CPU variants exactly are supported by the assembly code in wolfssl. Fixes: - MIPS64 case: http://autobuild.buildroot.net/results/43e/43ee1a457cbeb986d958c9a70cac0676377661c0/ - RISC-V case: http://autobuild.buildroot.net/results/f05/f056ebe7749a69994afba39a9d4967e2774c45ea/ Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> |
||
---|---|---|
arch | ||
board | ||
boot | ||
configs | ||
docs | ||
fs | ||
linux | ||
package | ||
support | ||
system | ||
toolchain | ||
utils | ||
.checkpackageignore | ||
.clang-format | ||
.defconfig | ||
.flake8 | ||
.gitignore | ||
.gitlab-ci.yml | ||
.shellcheckrc | ||
CHANGES | ||
Config.in | ||
Config.in.legacy | ||
COPYING | ||
DEVELOPERS | ||
Makefile | ||
Makefile.legacy | ||
README |
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