On 2/2/2026 8:45 PM, Yoann Congal via lists.openembedded.org wrote:
**
*CAUTION: This email comes from a non Wind River email account!*
Do not click links or open attachments unless you recognize the sender and know the content is safe.


Le dim. 1 févr. 2026 à 08:52, Mathieu Dubois-Briand via lists.openembedded.org <http://lists.openembedded.org> <[email protected]> a écrit :

    On Fri Jan 30, 2026 at 2:41 PM CET, Hemanth.KumarMD via
    lists.openembedded.org <http://lists.openembedded.org> wrote:
    > From: Hemanth Kumar M D <[email protected]>
    >
    > https://blog.rust-lang.org/2026/01/22/Rust-1.93.0/
    > Rust changes: https://github.com/rust-lang/rust/releases/tag/1.93.0
    > Cargo changes:
    https://doc.rust-lang.org/nightly/cargo/CHANGELOG.html#cargo-193-2026-01-22
    >
    > * rust-oe-selftest.patch updated for 1.93:
    >   Renamed UI test directive from add-core-stubs to add-minicore
    as in
    >
    
https://github.com/rust-lang/rust/commit/3796f7de57f5d4cf4325d1f13aeb07fdaa57983b
    >
    > * OE-selftests:
    >   - Exclude src/tools/remote-test-client from test suite.
    >     This unit test modifies the TEST_DEVICE_ADDR environment
    variable,
    >     which breaks the OE test harness that uses the same variable for
    >     QEMU remote testing. Filed a bug with upstream:
    > https://github.com/rust-lang/rust/issues/151823
    >
    >   - Enable +v8a feature for cortexa57.
    >     Rust 1.93.0 added a regression test (PR #149549) to verify
    that the
    >     ARMv8-A system register ttbr0_el2 is recognized in inline
    assembly.
    >     This addresses issue #97724 where LLVM wasn't recognizing
    ttbr0_el2
    >     as a valid register. Upstream Rust enables +v8a by default
    for all
    >     AArch64 targets (PR #105026), but Yocto's custom target
    specification
    >     doesn't inherit this. Adding +v8a ensures LLVM recognizes
    ARMv8-A
    >     system registers, fixing the test failure.
    >
    >     Related upstream links:
    >     - PR #149549: https://github.com/rust-lang/rust/pull/149549
    >     - Issue #97724: https://github.com/rust-lang/rust/issues/97724
    >     - PR #105026: https://github.com/rust-lang/rust/pull/105026
    >
    > Test results:
    >
    > rust v1.93.0
    > +-------------+--------+---------+
    > | Machine     | Passed | Skipped |
    > +-------------+--------+---------+
    > | qemux86-64  | 21,689 |   646   |
    > | qemux86     | 21,439 |   896   |
    > | qemuarm64   | 21,495 |   840   |
    > | qemuarm     | 21,421 |   914   |
    > | qemuriscv64 | 21,466 |   869   |
    > +-------------+--------+---------+
    >
    > Test results difference (1.93.0 - 1.92.0):
    >
    > +-------------+--------+---------+
    > | Machine     | Passed | Skipped |
    > +-------------+--------+---------+
    > | qemux86-64  |  +205  |   +33   |
    > | qemux86     |  +205  |   +33   |
    > | qemuarm64   |  +206  |   +32   |
    > | qemuarm     |  +205  |   +33   |
    > | qemuriscv64 |  +205  |   +33   |
    > +-------------+--------+---------+
    >
    > Signed-off-by: Hemanth Kumar M D <[email protected]>
    > ---

    Hi Hemanth,

    Thanks for the upgrade.

    I suspect this is responsible of the
    runtime_test.RustKernel.test_kernel_rust_sample selftest failure:

    2026-01-31 16:20:41,991 - oe-selftest - INFO -
    runtime_test.RustKernel.test_kernel_rust_sample
    (subunit.RemotedTestCase)
    2026-01-31 16:20:41,994 - oe-selftest - INFO -  ... FAIL
    ...
    ERROR: linux-yocto-6.16.11+git-r0 do_compile: Execution of
    
'/srv/pokybuild/yocto-worker/oe-selftest-debian/build/build-st-766138/tmp/work/qemux86_64-poky-linux/linux-yocto/6.16.11+git/temp/run.do_compile.189616'
    failed with exit code 1
    ...
    | error: unknown unstable option: `no-jump-tables`

    https://autobuilder.yoctoproject.org/valkyrie/#/builders/35/builds/3127
    https://autobuilder.yoctoproject.org/valkyrie/#/builders/48/builds/3022

    Can you have a look at what is going wrong here?


Hello,

To clarify because this is not totally obvious:
This test is defined in the "[PATCH v5 00/15] Enable rust support for linux kernel" from Harish.Sadineni (also at Windriver)
https://lore.kernel.org/openembedded-core/[email protected]/
So, the test is not present on master (or even master-next).
Hi all,

"[PATCH v5 00/15] Enable rust support for linux kernel" this series is taken to mathieu/msater-next, on top of this series when testing with rust-1.93.0 patch
has caused this build failure.

This failure is already identified in upstream and has a fix in linux-kernel 6.18/master, so i will send a backport fix to linux-yocto v6.16.
https://github.com/torvalds/linux/commit/789521b4717fd6bd85164ba5c131f621a79c9736

Can the rust 1.93.0 patch be tested/merged , By the time above mentioned backported patch taken to linux-yocto v6.16?.


    Thanks,
    Mathieu

-- Mathieu Dubois-Briand, Bootlin
    Embedded Linux and Kernel engineering
    https://bootlin.com






--
Yoann Congal
Smile ECS



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#230376): 
https://lists.openembedded.org/g/openembedded-core/message/230376
Mute This Topic: https://lists.openembedded.org/mt/117544255/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to