All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Burton <Ross.Burton@arm.com>
To: "bruce.ashfield@gmail.com" <bruce.ashfield@gmail.com>
Cc: Khem Raj <raj.khem@gmail.com>,
	Richard Purdie <richard.purdie@linuxfoundation.org>,
	openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] gcc12 testing results
Date: Mon, 9 May 2022 11:51:59 +0000	[thread overview]
Message-ID: <F23D7126-B6EF-430A-B3D4-36979D9A9A1B@arm.com> (raw)
In-Reply-To: <CADkTA4PLxeGwEau+DC7c=hQdw4Ro4bTz08xtK_YNHk_jO2N_hA@mail.gmail.com>


> On 6 May 2022, at 17:08, Bruce Ashfield via lists.openembedded.org <bruce.ashfield=gmail.com@lists.openembedded.org> wrote:
>
> On Fri, May 6, 2022 at 11:41 AM Khem Raj <raj.khem@gmail.com> wrote:
>>
>> yeah meta-virt is seemingly a new addition. Adding Bruce also about
>> the failures.
>
> The Xen guys will hopefully get around to it shortly, but we are still
> going through significant work to get kirkstone stabilized and
> released for meta-virt, so there's unlikely to be anything specific
> done on it for a bit yet.
>
> I'm sure Xen upstream has already addressed it, but our Xen upgrades
> are in place for the release (Which is where the stabilization effort
> is happening), so we can peek for incremental fixes as appropriate.

At least OpenSuse has a workaround patch:

https://build.opensuse.org/package/view_file/openSUSE:Factory/xen/gcc12-fixes.patch?expand=1

I’m pretty sure we can’t expect to see that upstreamed, but its likely good enough for the short term.

Ross
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

  parent reply	other threads:[~2022-05-09 11:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-06 15:14 gcc12 testing results richard.purdie
2022-05-06 15:41 ` Khem Raj
2022-05-06 16:08   ` Bruce Ashfield
2022-05-07  4:46     ` Khem Raj
2022-05-09 11:51     ` Ross Burton [this message]
2022-05-07  4:42 ` Khem Raj
2022-05-08  7:51   ` richard.purdie
2022-05-09 13:24 ` [OE-core] " Bruce Ashfield
2022-05-09 15:27   ` Khem Raj
2022-05-09 16:34   ` richard.purdie
2022-05-09 16:52     ` Khem Raj

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=F23D7126-B6EF-430A-B3D4-36979D9A9A1B@arm.com \
    --to=ross.burton@arm.com \
    --cc=bruce.ashfield@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=richard.purdie@linuxfoundation.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.