public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
	 mark.hatle@kernel.crashing.org
Cc: openembedded-core@lists.openembedded.org, Paul Barker <paul@pbarker.dev>
Subject: Re: [OE-core] [PATCH v2 7/7] rust-target-config.bbclass: Update for new riscv TUNE_FEATURES
Date: Wed, 14 Jan 2026 10:33:14 +0000	[thread overview]
Message-ID: <4ba4ca643eb20de0eddbcb4895598d22831b12be.camel@linuxfoundation.org> (raw)
In-Reply-To: <CANNYZj-7dDr=UwCzDHW-EqMRPWvsSKX3DABLoAtQx1D0ba8k7g@mail.gmail.com>

On Wed, 2026-01-14 at 11:16 +0100, Alexander Kanavin wrote:
> On Wed, 18 Jun 2025 at 01:39, Mark Hatle via lists.openembedded.org
> <mark.hatle=kernel.crashing.org@lists.openembedded.org> wrote:
> > -        tspec['llvm-abiname'] = "lp64d"
> > +        tspec['llvm-abiname'] = d.getVar('TUNE_RISCV_ABI')
> >      if "riscv32" in tspec['llvm-target']:
> > -        tspec['llvm-abiname'] = "ilp32d"
> > +        tspec['llvm-abiname'] = d.getVar('TUNE_RISCV_ABI')
> 
> Unfortunately this adds a dependency on TUNE_RISCV_ABI (which is set
> only if the target is a risc-v machine) to rust-native's
> rust_gen_targets task, breaking sstate reuse for it between risc-v and
> any other target. I can imagine other native pieces written in rust
> will have the same issue.
> 
> It's not immediately obvious to me how to address this, so I'd really
> appreciate suggestions. The code is hairy.
> 
> Ticket: https://bugzilla.yoctoproject.org/show_bug.cgi?id=16132

Nice find. I worry about our sstate tests not covering this. We might need to do:

-rust_gen_target[vardepsexclude] += "ABIEXTENSION llvm_cpu"
+rust_gen_target[vardepsexclude] += "ABIEXTENSION llvm_cpu TUNE_RISCV_ABI"

Cheers,

Richard



  reply	other threads:[~2026-01-14 10:33 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-17 23:39 [PATCH v2 0/7] ISA based RISC-V tune implementation Mark Hatle
2025-06-17 23:39 ` [PATCH v2 1/7] riscv tunes: ISA Implementation of RISC-V tune features Mark Hatle
2025-06-18  4:00   ` [OE-core] " Alistair Francis
2025-06-18 14:12     ` Mark Hatle
     [not found]     ` <184A2891E949D242.11882@lists.openembedded.org>
2025-06-18 16:50       ` Mark Hatle
2025-06-17 23:39 ` [PATCH v2 2/7] linux-yocto: Enable risc-v TUNE_FEATURES ISA selections ** DO NOT MERGE ** Mark Hatle
2025-06-17 23:39 ` [PATCH v2 3/7] u-boot: Dynamic RISC-V ISA configuration Mark Hatle
2025-06-17 23:39 ` [PATCH v2 4/7] qemuriscv: Dynamically configure qemu CPU Mark Hatle
2025-06-17 23:39 ` [PATCH v2 5/7] features_check.bbclass: Add support for required TUNE_FEATURES Mark Hatle
2025-06-17 23:39 ` [PATCH v2 6/7] kernel.bbclass: State riscv required tune_features for Linux Mark Hatle
2025-06-17 23:39 ` [PATCH v2 7/7] rust-target-config.bbclass: Update for new riscv TUNE_FEATURES Mark Hatle
2026-01-14 10:16   ` [OE-core] " Alexander Kanavin
2026-01-14 10:33     ` Richard Purdie [this message]
2026-01-14 10:50       ` Alexander Kanavin
2026-01-14 10:57         ` Richard Purdie
2025-06-18 19:29 ` [OE-core] [PATCH v2 0/7] ISA based RISC-V tune implementation Gyorgy Sarvari

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=4ba4ca643eb20de0eddbcb4895598d22831b12be.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=alex.kanavin@gmail.com \
    --cc=mark.hatle@kernel.crashing.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul@pbarker.dev \
    /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