diff options
author | David Gow <davidgow@google.com> | 2024-05-29 17:33:35 +0800 |
---|---|---|
committer | Johannes Berg <johannes.berg@intel.com> | 2024-07-03 12:22:11 +0200 |
commit | 9a2123b397bbe0da5e853273369d63779ac97c8c (patch) | |
tree | d3a1f2ac203c0fbbcad93f5d282da26f4dbc5075 /scripts/generate_rust_target.rs | |
parent | cb2759431acae9c6093f6f4cb270e3a3bd0f4e73 (diff) | |
download | linux-stable-9a2123b397bbe0da5e853273369d63779ac97c8c.tar.gz linux-stable-9a2123b397bbe0da5e853273369d63779ac97c8c.tar.bz2 linux-stable-9a2123b397bbe0da5e853273369d63779ac97c8c.zip |
arch: um: rust: Use the generated target.json again
The Rust compiler can take a target config from 'target.json', which is
generated by scripts/generate_rust_target.rs. It used to be that all
Linux architectures used this to generate a target.json, but now
architectures must opt-in to this, or they will default to the Rust
compiler's built-in target definition.
This is mostly okay for (64-bit) x86 and UML, except that it can
generate SSE instructions, which we can't use in the kernel. So
re-instate the custom target.json, which disables SSE (and generally
enables the 'soft-float' feature). This fixes the following compile
error:
error: <unknown>:0:0: in function _RNvMNtCs5QSdWC790r4_4core3f32f7next_up float (float): SSE register return with SSE disabled
Fixes: f82811e22b48 ("rust: Refactor the build target to allow the use of builtin targets")
Signed-off-by: David Gow <davidgow@google.com>
Reviewed-by: Boqun Feng <boqun.feng@gmail.com>
Tested-by: Miguel Ojeda <ojeda@kernel.org>
Reviewed-by: Miguel Ojeda <ojeda@kernel.org>
Link: https://patch.msgid.link/20240529093336.4075206-1-davidgow@google.com
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'scripts/generate_rust_target.rs')
0 files changed, 0 insertions, 0 deletions