All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Dora, Sunil Kumar" <SunilKumar.Dora@windriver.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: clang/llvm 23.1.0 upgrade for oe-core
Date: Sat, 29 Aug 2026 07:22:53 -0700	[thread overview]
Message-ID: <2894840.1788013373272673695@lists.openembedded.org> (raw)
In-Reply-To: <2894840.1787984583874976123@lists.openembedded.org>

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

Hi all,

While testing the clang/llvm 23.1.0 upgrade with 32-bit multilib, lib32-llvm failed to build. LLVM 23's APFloat.cpp
now pulls in llvm-libc float16 headers, and their detection breaks on i686 without SSE2 with GCC >= 14.
The build dies with "SSE register return with SSE2 disabled". LLVM 22.1.8 was not affected.

I reported it upstream and sent a one-line fix:

https://github.com/llvm/llvm-project/issues/219668
https://github.com/llvm/llvm-project/pull/219675

Until that lands in a release, the series carries the patch with Upstream-Status: Submitted.

The same multilib round also caught an openmp packaging problem (installed into lib/ instead of lib64/), fixed in the openmp recipe by passing LLVM_LIBDIR_SUFFIX like the other clang-family recipes.

I am running a final round of local testing with both fixes and will post the updated series after that.

Thanks,
Sunil Dora

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

  reply	other threads:[~2026-08-29 14:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DS0PR11MB7901641887C85593E522BD3BE0AC2@DS0PR11MB7901.namprd11.prod.outlook.com>
2026-08-28 23:36 ` clang/llvm 23.1.0 upgrade for oe-core Khem Raj
2026-08-29  2:28   ` Dora, Sunil Kumar
2026-08-29  6:23   ` Dora, Sunil Kumar
2026-08-29 14:22     ` Dora, Sunil Kumar [this message]
2026-08-28 17:14 Dora, Sunil Kumar

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=2894840.1788013373272673695@lists.openembedded.org \
    --to=sunilkumar.dora@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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.