diff options
| author | Nathan Rossi <nathan@nathanrossi.com> | 2020-12-15 08:34:58 +0000 |
|---|---|---|
| committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2021-01-04 11:45:47 +0000 |
| commit | bd166d6318a2c575a0ad0f1ac4ccc7eef848eadd (patch) | |
| tree | 1edd9350f2fff3087ac1d1a210c502c81370bde3 /meta/recipes-connectivity/bluez5 | |
| parent | 6de89a57c44ddd0ce78ff1b9bd3fc2dbbe7e83cc (diff) | |
| download | poky-bd166d6318a2c575a0ad0f1ac4ccc7eef848eadd.tar.gz | |
gcc: Add patch to resolve i*86 tune configuration overrides
When compiling gcc-runtime for i686 libatomic, libgomp and libitm are
compiled with additional '-march' and '-mtune' overrides. This typically
does not cause build errors (e.g. core2-32 tune), and results in less
optimally tuned outputs. However with specific TUNE_CCARGS (e.g. has
'-mfpmath=sse' but not '-msse*'), the build errors with conflicting
'-mfpmath' options.
This is caused by gcc-runtime specific configure scripts and Makefile
options that override by adding additional '-march'/'-mtune' args. OE
builds gcc-runtime differently to other build systems, and provides
target specific arch/tune options directly. As such, this change adds a
patch for gcc to remove the specific cases where the args are added.
(From OE-Core rev: 5ce0102ca75754f0a7c777505678677cdf2a62bc)
Signed-off-by: Nathan Rossi <nathan@nathanrossi.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(cherry picked from commit d39b686cc5fcc89405ffeb560ea64b5d305b0608)
Signed-off-by: Anuj Mittal <anuj.mittal@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/recipes-connectivity/bluez5')
0 files changed, 0 insertions, 0 deletions