The x86 rust gcc builds failed on the Linux next-20240917 due to following build warnings / errors with rustgcc for selftests rust builds.
First seen on next-20240917 Good: next-20240913 BAD: next-20240917
Reported-by: Linux Kernel Functional Testing lkft@linaro.org
build log: -------- error: unknown unstable option: `patchable-function-entry`
make[3]: *** [rust/Makefile:392: rust/core.o] Error 1
Build Log links, -------- - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240916/tes...
Build failed comparison: - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20240916/tes...
metadata: ---- git describe: next-20240917 git repo: https://gitlab.com/Linaro/lkft/mirrors/next/linux-next git sha: 7083504315d64199a329de322fce989e1e10f4f7 kernel config: https://storage.tuxsuite.com/public/linaro/lkft/builds/2m9CHpK6gWVXL2Rjt0R5T... build url: https://storage.tuxsuite.com/public/linaro/lkft/builds/2m9CHpK6gWVXL2Rjt0R5T... toolchain: rustgcc config-name: rustgcc-lkftconfig-kselftest arch: x86
Steps to reproduce: --------- - https://storage.tuxsuite.com/public/linaro/lkft/builds/2m9CHpK6gWVXL2Rjt0R5T... - tuxmake --runtime podman \ --target-arch x86_64 \ --toolchain rustgcc \ --kconfig https://storage.tuxsuite.com/public/linaro/lkft/builds/2m9CHpK6gWVXL2Rjt0R5T... \ TARGETS=rust debugkernel cpupower headers kernel kselftest modules
-- Linaro LKFT https://lkft.linaro.org
Hi Naresh,
On Mon, Sep 16, 2024 at 9:17 PM Naresh Kamboju naresh.kamboju@linaro.org wrote:
The x86 rust gcc builds failed on the Linux next-20240917 due to following build warnings / errors with rustgcc for selftests rust builds.
First seen on next-20240917 Good: next-20240913 BAD: next-20240917
Reported-by: Linux Kernel Functional Testing lkft@linaro.org
Thanks for the report -- this should be already fixed in `rust-next` for tomorrow (requirement changed from `!FINEIBT` to `!CALL_PADDING`), please see https://lore.kernel.org/rust-for-linux/CANiq72=B9NmC=1eSaOrg7XutjueQsSXGcBQb...
If you can confirm it is, that would be great, thanks! i.e. you will need either to disable `CALL_PADDING` or use a newer Rust compiler version.
By the way, I think you meant next-202409176, not next-20240917?
Cheers, Miguel
On Tue, 17 Sept 2024 at 00:53, Miguel Ojeda miguel.ojeda.sandonis@gmail.com wrote:
Hi Naresh,
On Mon, Sep 16, 2024 at 9:17 PM Naresh Kamboju naresh.kamboju@linaro.org wrote:
The x86 rust gcc builds failed on the Linux next-20240917 due to following build warnings / errors with rustgcc for selftests rust builds.
First seen on next-20240917 Good: next-20240913 BAD: next-20240917
Reported-by: Linux Kernel Functional Testing lkft@linaro.org
Thanks for the report -- this should be already fixed in `rust-next` for tomorrow (requirement changed from `!FINEIBT` to `!CALL_PADDING`), please see https://lore.kernel.org/rust-for-linux/CANiq72=B9NmC=1eSaOrg7XutjueQsSXGcBQb...
If you can confirm it is, that would be great, thanks! i.e. you will need either to disable `CALL_PADDING` or use a newer Rust compiler version.
I will try to use the newer Rust Compiler.
By the way, I think you meant next-202409176, not next-20240917?
Right, I mean next-20240916.
- Naresh
Cheers, Miguel
-
Miguel Ojeda -
Naresh Kamboju