mirror of
https://git.yoctoproject.org/poky
synced 2026-02-20 08:29:42 +01:00
156a2d9860
tune files which inherit the arch definitions already define appropriate -mcpu option, which is equivalent of right -march and -mtune combination and is preferred since gcc is getting stricter and stricter with option check semantics and can now find incompatible -march and -mcpu options better with every release. It does internal feature consistency check and if it finds out discrepency between what -mcpu would expand to as compared to -march it will flag the options to be incompatible, for naked eye it sounds wrong but gcc would translate -mcpu to a given -march internally and it might not match to what we set in these arch files. The effects are quite subtle, where this can result in configure test failing to compile due to these incompatible options and a feature option getting disabled for a recipe for no reason. e.g. with gcc9 which can now detect that -mcpu=cortex-a5 and -march=armv7-a are incompatible, many features in libstdc++ ends up disabled due to configure check failures e.g. size_t size, ptrdiff_t sizes, which inturn results in compiling libstdc++ with unwanted disabled features. (From OE-Core rev: ac83d22eb5031f7fdd09d34a1a46d92fd3e39a3c) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
14 lines
583 B
PHP
14 lines
583 B
PHP
DEFAULTTUNE ?= "armv4t"
|
|
|
|
require conf/machine/include/arm/arch-armv4.inc
|
|
|
|
TUNEVALID[arm920t] = "Enable arm920t specific processor optimizations"
|
|
TUNE_CCARGS .= "${@bb.utils.contains('TUNE_FEATURES', 'arm920t', ' -mcpu=arm920t', '', d)}"
|
|
MACHINEOVERRIDES =. "${@bb.utils.contains('TUNE_FEATURES', 'arm920t', 'armv4:', '' ,d)}"
|
|
|
|
AVAILTUNES += "arm920t"
|
|
ARMPKGARCH_tune-arm920t = "arm920t"
|
|
# mcpu is used so don't use armv4t as we don't want march
|
|
TUNE_FEATURES_tune-arm920t = "arm thumb arm920t"
|
|
PACKAGE_EXTRA_ARCHS_tune-arm920t = "${PACKAGE_EXTRA_ARCHS_tune-armv4t} arm920t arm920tt"
|