Re: [OE-core] [PATCH v2 2/3] rust: Upgrade 1.84.1->1.85.0

[Yash Shinde <Yash.Shinde@windriver.com>]

[-- Attachment #1: Type: text/plain, Size: 1515 bytes --]


On 15-04-2025 17:08, Martin Jansa wrote:
> qemuarmv5 uses tune-arm926ejs which uses armv5te, I think you would
> need to use armv5te-vfp to reproduce this, or use qemuarm with
> tune-cortexa15 but switch from default cortexa15thf-neon to
> cortexa15t-neon
>
> I was seeing it in multilib builds e.g. with
> https://git.openembedded.org/openembedded-core-contrib/commit/?h=jansa/master&id=40e9c4744a7f1eb2d91af9539d69555d36dfba30
> which uses DEFAULTTUNE:virtclass-multilib-lib32 = "armv7at-neon"
>
> unfortunately just treating softfp as soft ends with segfaults in rust
> as shown nere:
> https://git.openembedded.org/openembedded-core-contrib/commit/?h=jansa/master&id=c65eda95e5dd3ad0be0565477236d7902d5d625c
>
> Regards,
>
> On Tue, Apr 15, 2025 at 11:05 AM Yash Shinde<Yash.Shinde@windriver.com> wrote:
I checked for softfp tuning using (which gave TARGET_FPU = softfp):

TUNE_FEATURES = "vfp armv5te"
DEFAULTTUNE = "armv5te-vfp"
TUNE_PKGARCH = "armv5te-vfp"

But, it seems that softfp is not a valid value for llvm-floatabi in rust.
It gives error as follows:

| --- stderr
| error: Error loading target specification: 'softfp' is not a valid 
value for llvm-floatabi. Use 'soft' or 'hard'.. Run `rustc --print 
target-list` for a list of built-in targets As you mentioned, using soft 
instead of softfp also doesn't work either. It seems that unless 
upstream Rust provides support for this, we won't be able to build Rust 
with softfp on ARM targets. Regards, Yash.



[-- Attachment #2: Type: text/html, Size: 2863 bytes --]