From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: "Anuj Mittal" <anuj.mittal@intel.com>,
"Bruce Ashfield" <bruce.ashfield@gmail.com>
Cc: <raj.khem@gmail.com>, <openembedded-core@lists.openembedded.org>,
"Joshua Watt" <JPEWhacker@gmail.com>, <martin.jansa@gmail.com>,
<richard.purdie@linuxfoundation.org>,
"swat" <swat@lists.yoctoproject.org>
Subject: Re: [OE-core] [PATCH v3] gcc: Upgrade GCC to 15 release
Date: Mon, 05 May 2025 10:18:25 +0200 [thread overview]
Message-ID: <D9O2V8V3WK87.2HZ8Q0QX1AL5W@bootlin.com> (raw)
In-Reply-To: <CA+chaQchL+vr2WSLtvoxRLTeEVb0Rk3wsrAQ4tNYYAY5aRdncA@mail.gmail.com>
On Tue Apr 29, 2025 at 12:10 PM CEST, Martin Jansa via lists.openembedded.org wrote:
> On Mon, Apr 28, 2025 at 10:54 PM Richard Purdie via
> lists.openembedded.org
> <richard.purdie=linuxfoundation.org@lists.openembedded.org> wrote:
>>
>> On Sat, 2025-04-26 at 16:30 -0700, Khem Raj via lists.openembedded.org
>> wrote:
>> > * Nios2 has been removed and aarch64/ilp32 is deprecated
>> > * Default C dialect is switched to C23
>> > * {0} initializer in C or C++ for unions no longer guarantees
>> > clearing of the whole union
>> > * Compile speed improvements with LTO
>> > * Vectorizer can support loops with early exists but it is limited to
>> > loops
>> > with fixed vector lengths
>> >
>> > This is major release of gcc, the changes are noted [1]
>> >
>> > [1] https://gcc.gnu.org/gcc-15/changes.html
>> >
>> > Signed-off-by: Khem Raj <raj.khem@gmail.com>
>> > ---
>> > v2: Drop musl headers ordering patch
>> > v3: Rebased patches
>>
>> We're getting much closer. My selftest-ed change nearly worked, I'll
>> try a new version of that. If that works, we have left:
>>
>> util-linux ptest regression:
>> https://autobuilder.yoctoproject.org/valkyrie/#/builders/73/builds/1396
>> https://autobuilder.yoctoproject.org/valkyrie/#/builders/61/builds/1393
>>
>> meta-mingw failure in libiconv:
>> https://autobuilder.yoctoproject.org/valkyrie/#/builders/7/builds/1521
>>
>> meta-intel failure in intel-mediasdk and intel-media-driver:
>> https://autobuilder.yoctoproject.org/valkyrie/#/builders/41/builds/1389
>>
>> meta-virtualization in ipxe:
>> https://autobuilder.yoctoproject.org/valkyrie/#/builders/89/builds/1402
>
> I'm seeing few more failures from meta-virtualization with gcc-15:
> http://errors.yoctoproject.org/Errors/Build/205175/
>
> I've sent fixes for ipxe, irqbalance and work around for libvmi, which
> leaves dev86 from meta-virtualization (where the repo from SRC_URI
> doesn't even exist anymore).
>
> Cheers,
Hi Anuj, Hi Bruce,
These patches have now been merged on master, so we had build failures
for a few days now on the said recipes.
mesa-intel:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/41/builds/1426
meta-virt:
https://autobuilder.yoctoproject.org/valkyrie/#/builders/89/builds/1439
Best regards,
Mathieu
--
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2025-05-05 8:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-26 23:30 [PATCH v3] gcc: Upgrade GCC to 15 release Khem Raj
2025-04-28 20:54 ` [OE-core] " Richard Purdie
2025-04-29 10:10 ` Martin Jansa
2025-05-05 8:18 ` Mathieu Dubois-Briand [this message]
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=D9O2V8V3WK87.2HZ8Q0QX1AL5W@bootlin.com \
--to=mathieu.dubois-briand@bootlin.com \
--cc=JPEWhacker@gmail.com \
--cc=anuj.mittal@intel.com \
--cc=bruce.ashfield@gmail.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=richard.purdie@linuxfoundation.org \
--cc=swat@lists.yoctoproject.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.