From: Boqun Feng <boqun.feng@gmail.com>
To: Miguel Ojeda <ojeda@kernel.org>
Cc: "Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Nathan Chancellor" <nathan@kernel.org>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
"Benno Lossin" <benno.lossin@proton.me>,
"Andreas Hindborg" <a.hindborg@samsung.com>,
"Alice Ryhl" <aliceryhl@google.com>,
rust-for-linux@vger.kernel.org,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Bill Wendling" <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>,
llvm@lists.linux.dev, linux-kernel@vger.kernel.org,
patches@lists.linux.dev
Subject: Re: [PATCH] rust: add intrinsics to fix `-Os` builds
Date: Tue, 6 Aug 2024 10:27:17 -0700 [thread overview]
Message-ID: <ZrJc9UE3xAV1ezdG@boqun-archlinux> (raw)
In-Reply-To: <20240806150619.192882-1-ojeda@kernel.org>
On Tue, Aug 06, 2024 at 05:06:19PM +0200, Miguel Ojeda wrote:
> Alice reported [1] that an arm64 build failed with:
>
> ld.lld: error: undefined symbol: __extendsfdf2
> >>> referenced by core.a6f5fc5794e7b7b3-cgu.0
> >>> rust/core.o:(<f32>::midpoint) in archive vmlinux.a
> >>> referenced by core.a6f5fc5794e7b7b3-cgu.0
> >>> rust/core.o:(<f32>::midpoint) in archive vmlinux.a
>
> ld.lld: error: undefined symbol: __truncdfsf2
> >>> referenced by core.a6f5fc5794e7b7b3-cgu.0
> >>> rust/core.o:(<f32>::midpoint) in archive vmlinux.a
>
> Rust 1.80.0 or later together with `CONFIG_CC_OPTIMIZE_FOR_SIZE=y`
> is what triggers it.
>
> In addition, x86_64 builds also fail the same way.
>
> Similarly, compiling with Rust 1.82.0 (currently in nightly) makes
> another one appear, possibly due to the LLVM 19 upgrade there:
>
> ld.lld: error: undefined symbol: __eqdf2
> >>> referenced by core.20495ea57a9f069d-cgu.0
> >>> rust/core.o:(<f64>::next_up) in archive vmlinux.a
> >>> referenced by core.20495ea57a9f069d-cgu.0
> >>> rust/core.o:(<f64>::next_down) in archive vmlinux.a
>
> Gary adds [1]:
>
> > Usually the fix on rustc side is to mark those functions as `#[inline]`
> >
> > All of {midpoint,next_up,next_down} are indeed unstable functions not
> > marked as inline...
>
> Fix all those by adding those intrinsics to our usual workaround.
>
> Cc: Gary Guo <gary@garyguo.net>
> Reported-by: Alice Ryhl <aliceryhl@google.com>
> Closes: https://rust-for-linux.zulipchat.com/#narrow/stream/288089-General/topic/v6.2E11-rc1.20doesn't.20build.20for.20arm64/near/455637364
> Signed-off-by: Miguel Ojeda <ojeda@kernel.org>
Put this one into rust-dev and confirm this could fix the issue with
Rust 1.80. I also add a test with CONFIG_CC_OPTIMIZE_FOR_SIZE=y in my
rust-dev script, so we can catch the similar issues earlier.
Tested-by: Boqun Feng <boqun.feng@gmail.com>
Regards,
Boqun
> ---
> rust/Makefile | 4 ++--
> rust/compiler_builtins.rs | 3 +++
> 2 files changed, 5 insertions(+), 2 deletions(-)
>
> diff --git a/rust/Makefile b/rust/Makefile
> index 1f10f92737f2..77836388377d 100644
> --- a/rust/Makefile
> +++ b/rust/Makefile
> @@ -354,8 +354,8 @@ rust-analyzer:
> $(if $(KBUILD_EXTMOD),$(extmod_prefix),$(objtree))/rust-project.json
>
> redirect-intrinsics = \
> - __addsf3 __eqsf2 __gesf2 __lesf2 __ltsf2 __mulsf3 __nesf2 __unordsf2 \
> - __adddf3 __ledf2 __ltdf2 __muldf3 __unorddf2 \
> + __addsf3 __eqsf2 __extendsfdf2 __gesf2 __lesf2 __ltsf2 __mulsf3 __nesf2 __truncdfsf2 __unordsf2 \
> + __adddf3 __eqdf2 __ledf2 __ltdf2 __muldf3 __unorddf2 \
> __muloti4 __multi3 \
> __udivmodti4 __udivti3 __umodti3
>
> diff --git a/rust/compiler_builtins.rs b/rust/compiler_builtins.rs
> index bba2922c6ef7..f14b8d7caf89 100644
> --- a/rust/compiler_builtins.rs
> +++ b/rust/compiler_builtins.rs
> @@ -40,16 +40,19 @@ pub extern "C" fn $ident() {
> define_panicking_intrinsics!("`f32` should not be used", {
> __addsf3,
> __eqsf2,
> + __extendsfdf2,
> __gesf2,
> __lesf2,
> __ltsf2,
> __mulsf3,
> __nesf2,
> + __truncdfsf2,
> __unordsf2,
> });
>
> define_panicking_intrinsics!("`f64` should not be used", {
> __adddf3,
> + __eqdf2,
> __ledf2,
> __ltdf2,
> __muldf3,
>
> base-commit: de9c2c66ad8e787abec7c9d7eff4f8c3cdd28aed
> --
> 2.46.0
>
>
next prev parent reply other threads:[~2024-08-06 17:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 15:06 [PATCH] rust: add intrinsics to fix `-Os` builds Miguel Ojeda
2024-08-06 15:41 ` Alice Ryhl
2024-08-06 17:27 ` Boqun Feng [this message]
2024-08-06 17:30 ` Miguel Ojeda
2024-08-06 18:30 ` Trevor Gross
2024-08-06 21:14 ` Miguel Ojeda
2024-08-07 13:03 ` Gary Guo
2024-08-09 22:10 ` Miguel Ojeda
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZrJc9UE3xAV1ezdG@boqun-archlinux \
--to=boqun.feng@gmail.com \
--cc=a.hindborg@samsung.com \
--cc=alex.gaynor@gmail.com \
--cc=aliceryhl@google.com \
--cc=benno.lossin@proton.me \
--cc=bjorn3_gh@protonmail.com \
--cc=gary@garyguo.net \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=ojeda@kernel.org \
--cc=patches@lists.linux.dev \
--cc=rust-for-linux@vger.kernel.org \
--cc=wedsonaf@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).