diff options
author | Paul Burton <[email protected]> | 2019-01-28 23:16:22 +0000 |
---|---|---|
committer | Paul Burton <[email protected]> | 2019-01-29 11:50:58 -0800 |
commit | 67fc5dc8a541e8f458d7f08bf88ff55933bf9f9d (patch) | |
tree | 348be20f9f2f0a3376d9e48a75bb23607b7448cb /tools/testing/selftests/bpf | |
parent | 0648e50e548d881d025b9419a1a168753c8e2bf7 (diff) |
MIPS: VDSO: Include $(ccflags-vdso) in o32,n32 .lds builds
When generating vdso-o32.lds & vdso-n32.lds for use with programs
running as compat ABIs under 64b kernels, we previously haven't included
the compiler flags that are supposedly common to all ABIs - ie. those in
the ccflags-vdso variable.
This is problematic in cases where we need to provide the -m%-float flag
in order to ensure that we don't attempt to use a floating point ABI
that's incompatible with the target CPU & ABI. For example a toolchain
using current gcc trunk configured --with-fp-32=xx fails to build a
64r6el_defconfig kernel with the following error:
cc1: error: '-march=mips1' requires '-mfp32'
make[2]: *** [arch/mips/vdso/Makefile:135: arch/mips/vdso/vdso-o32.lds] Error 1
Include $(ccflags-vdso) for the compat VDSO .lds builds, just as it is
included for the native VDSO .lds & when compiling objects for the
compat VDSOs. This ensures we consistently provide the -msoft-float flag
amongst others, avoiding the problem by ensuring we're agnostic to the
toolchain defaults.
Signed-off-by: Paul Burton <[email protected]>
Fixes: ebb5e78cc634 ("MIPS: Initial implementation of a VDSO")
Cc: [email protected]
Cc: Kevin Hilman <[email protected]>
Cc: Guenter Roeck <[email protected]>
Cc: Maciej W . Rozycki <[email protected]>
Cc: [email protected] # v4.4+
Diffstat (limited to 'tools/testing/selftests/bpf')
0 files changed, 0 insertions, 0 deletions