From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
Ard Biesheuvel <ardb@kernel.org>
Subject: Re: Strange behavior between GCC 11 and GCC 12
Date: Mon, 17 Apr 2023 11:24:21 +0200 [thread overview]
Message-ID: <xistf7wxjdtwtuskzblgx6scexdwdmmugdqb5w6l6rtdgzkrnd@mrwxuw6lcyvr> (raw)
In-Reply-To: <653323a0-67d9-f896-83fe-46cf207fc83d@amd.com>
On Fri, Apr 14, 2023 at 04:39:23PM -0500, Tom Lendacky wrote:
> On 4/14/23 15:23, Tom Lendacky wrote:
> > I've been trying to debug a problem I'm seeing when I moved to the GCC 12
> > compiler. Under SEV it results in the guest crashing.
>
> False alarm, I was on the wrong branch that does not have ff36b2550f94
> ("OvmfPkg/Sec: fix stack switch")... disregard.
FYI: You need 129404f6e439 too.
HTH,
Gerd
next prev parent reply other threads:[~2023-04-17 9:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 20:23 Strange behavior between GCC 11 and GCC 12 Lendacky, Thomas
2023-04-14 21:39 ` Lendacky, Thomas
2023-04-17 9:24 ` Gerd Hoffmann [this message]
2023-04-14 21:39 ` Ard Biesheuvel
2023-04-14 21:50 ` Lendacky, Thomas
2023-04-15 0:49 ` [edk2-devel] " Ni, Ray
[not found] ` <1755F557A60CA0E1.29871@groups.io>
2023-04-15 5:04 ` Ni, Ray
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-list 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=xistf7wxjdtwtuskzblgx6scexdwdmmugdqb5w6l6rtdgzkrnd@mrwxuw6lcyvr \
--to=devel@edk2.groups.io \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox