From: Yash Shinde <Yash.Shinde@windriver.com>
To: Khem Raj <raj.khem@gmail.com>, koen.kooi@oss.qualcomm.com
Cc: openembedded-core@lists.openembedded.org,
Randy.MacLeod@windriver.com, Sundeep.Kokkonda@windriver.com
Subject: Re: [OE-core] [PATCH 2/3] rust: Upgrade 1.84.1->1.85.0
Date: Mon, 31 Mar 2025 11:22:52 +0530 [thread overview]
Message-ID: <0cfce4a9-6736-4bac-8eb9-d00a41c0b4b0@windriver.com> (raw)
In-Reply-To: <CAMKF1soMjq2unU3+i1iBVgPYZ=HEDY4SBdZ+Sx1DH1Po_p5TWw@mail.gmail.com>
On 28-03-2025 23:32, Khem Raj 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.
>
> On Fri, Mar 28, 2025 at 8:17 AM Koen Kooi via lists.openembedded.org
> <koen.kooi=oss.qualcomm.com@lists.openembedded.org> wrote:
>>
>>
>>> Op 28 mrt 2025, om 15:30 heeft Yash Shinde via lists.openembedded.org <Yash.Shinde=windriver.com@lists.openembedded.org> het volgende geschreven:
>>>
>>> From: Yash Shinde <Yash.Shinde@windriver.com>
>>>
>>> Rust stable version updated to 1.85.0
>>> https://blog.rust-lang.org/2025/02/20/Rust-1.85.0.html
>>>
>>> Some of the major updates:
>>> [...]
>>>
>>> - Explicitly set float ABI for all ARM 32 bits targets.
>>> Fix: https://github.com/rust-lang/rust/commit/a51fefcaab835b310e2e26005b50982d0049d905
>> In OE we allow selecting the ABI using tunefiles, so this hardcoding to hf will do the wrong thing for non-hf builds (which are rare, but still).
>>
> this commit has LLVM_FLOATABI introduced, which is what we can set
> based on tunes.
Thanks for the pointers.
I will update llvm-float ABI for rust target config based on
"TARGET_FPU" set in OE.
Regards,
Yash.
>> regards,
>>
>> Koen
>>
next prev parent reply other threads:[~2025-03-31 5:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-28 14:30 [PATCH 1/3] rust: Update "do_update_snapshot" task for rust-snapshot.inc Yash.Shinde
2025-03-28 14:30 ` [PATCH 2/3] rust: Upgrade 1.84.1->1.85.0 Yash.Shinde
2025-03-28 14:40 ` [OE-core] " Richard Purdie
2025-03-28 18:39 ` Alexander Kanavin
2025-03-31 5:51 ` Yash Shinde
2025-03-28 14:50 ` Patchtest results for " patchtest
2025-03-28 15:17 ` [OE-core] " Koen Kooi
2025-03-28 17:51 ` Richard Purdie
2025-03-31 5:52 ` Yash Shinde
2025-03-28 18:02 ` Khem Raj
2025-03-31 5:52 ` Yash Shinde [this message]
2025-03-28 20:56 ` Randy MacLeod
2025-03-29 15:26 ` Richard Purdie
2025-03-31 5:53 ` Yash Shinde
2025-03-28 14:30 ` [PATCH 3/3] rust: Upgrade 1.85.0->1.85.1 Yash.Shinde
2025-03-28 14:50 ` Patchtest results for " patchtest
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=0cfce4a9-6736-4bac-8eb9-d00a41c0b4b0@windriver.com \
--to=yash.shinde@windriver.com \
--cc=Randy.MacLeod@windriver.com \
--cc=Sundeep.Kokkonda@windriver.com \
--cc=koen.kooi@oss.qualcomm.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.