From: "Gerd Hoffmann" <kraxel@redhat.com>
To: Mike Beaton <mjsbeaton@gmail.com>
Cc: devel@edk2.groups.io, Ard Biesheuvel <ardb@kernel.org>,
Liming Gao <gaoliming@byosoft.com.cn>,
Rebecca Cran <rebecca@bsdio.com>,
Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] CLANGDWARF OVMF hangs on start
Date: Thu, 7 Dec 2023 10:31:18 +0100 [thread overview]
Message-ID: <p5xn5qum6kg3wynelezcquvomflqef7v3snwtcjxnqv5nd7qpx@yqf2crv47dxt> (raw)
In-Reply-To: <CAHzAAWQrTe6cw7fQeeTx_oRsBMTTs6zruRdj_m+P0J_9h_VGbQ@mail.gmail.com>
On Thu, Dec 07, 2023 at 08:40:55AM +0000, Mike Beaton wrote:
> From commit https://github.com/tianocore/edk2/commit/140e4422b16482f0bcafdc20d42141434d450450
> (and see also the preceding commit, which I believe is related) up to
> the current tip of master, CLANGDWARF OVMF is broken. It builds and
> starts but hangs early (more info below). I do not currently have a
> patch to offer though of course it would be useful if this could be
> resolved.
Which clang version is this?
It works for me, fedora 39 / clang 17, and I'm pretty sure I tested it
when creating the patch on a slightly older clang version (15 or 16).
take care,
Gerd
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#112174): https://edk2.groups.io/g/devel/message/112174
Mute This Topic: https://groups.io/mt/103030855/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2023-12-07 9:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 8:40 [edk2-devel] CLANGDWARF OVMF hangs on start Mike Beaton
2023-12-07 9:31 ` Gerd Hoffmann [this message]
2023-12-07 11:50 ` Mike Beaton
2023-12-07 12:53 ` Mike Beaton
2023-12-07 13:05 ` Mike Beaton
2023-12-09 15:24 ` Mike Beaton
2023-12-09 16:10 ` Mike Beaton
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=p5xn5qum6kg3wynelezcquvomflqef7v3snwtcjxnqv5nd7qpx@yqf2crv47dxt \
--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