[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALNs47swnK6je1o+LOLUFCDEZJmQmZx8vZ+7MPvUbNKdFr_Q_Q@mail.gmail.com>
Date: Tue, 6 Aug 2024 14:30:33 -0400
From: Trevor Gross <tmgross@...ch.edu>
To: Miguel Ojeda <ojeda@...nel.org>
Cc: Alex Gaynor <alex.gaynor@...il.com>, Wedson Almeida Filho <wedsonaf@...il.com>,
Nathan Chancellor <nathan@...nel.org>, Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
Benno Lossin <benno.lossin@...ton.me>, Andreas Hindborg <a.hindborg@...sung.com>,
Alice Ryhl <aliceryhl@...gle.com>, rust-for-linux@...r.kernel.org,
Nick Desaulniers <ndesaulniers@...gle.com>, Bill Wendling <morbo@...gle.com>,
Justin Stitt <justinstitt@...gle.com>, llvm@...ts.linux.dev, linux-kernel@...r.kernel.org,
patches@...ts.linux.dev
Subject: Re: [PATCH] rust: add intrinsics to fix `-Os` builds
On Tue, Aug 6, 2024 at 11:06 AM Miguel Ojeda <ojeda@...nel.org> 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@...yguo.net>
> Reported-by: Alice Ryhl <aliceryhl@...gle.com>
> Closes: https://rust-for-linux.zulipchat.com/#narrow/stream/288089-General/topic/v6.2E11-rc1.20doesn't.20build.20for.20arm64/near/455637364
Should this link have the `[1]`?
> Signed-off-by: Miguel Ojeda <ojeda@...nel.org>
> ---
> rust/Makefile | 4 ++--
> rust/compiler_builtins.rs | 3 +++
> 2 files changed, 5 insertions(+), 2 deletions(-)
Reviewed-by: Trevor Gross <tmgross@...ch.edu>
Also submitted a fix upstream https://github.com/rust-lang/rust/pull/128749.
- Trevor
Powered by blists - more mailing lists