From: "Marvin Häuser" <mhaeuser@posteo.de>
To: Pedro Falcato <pedro.falcato@gmail.com>
Cc: devel@edk2.groups.io, Bob Feng <bob.c.feng@intel.com>,
Liming Gao <gaoliming@byosoft.com.cn>,
Yuwei Chen <yuwei.chen@intel.com>,
Michael D Kinney <michael.d.kinney@intel.com>,
Leif Lindholm <quic_llindhol@quicinc.com>,
Andrew Fish <afish@apple.com>
Subject: Re: [edk2-devel] [PATCH 1/1] BaseTools: Fix IA32 UINT64 alignment for CLANG toolchains
Date: Fri, 16 Dec 2022 20:08:03 +0000 [thread overview]
Message-ID: <FC988F12-BC7C-4C99-8EA9-E9B5DE6F7313@posteo.de> (raw)
In-Reply-To: <CAKbZUD0t0bjhpgXNkbSXtEDAnSg164vLWb4JYFDvQHqw_3PEOg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 725 bytes --]
Revised version of last year’s https://edk2.groups.io/g/devel/message/79670
Initially caught by last year‘s https://edk2.groups.io/g/devel/message/79318
But now caught *yet again*, independently, via bugs during development.
Cc stewards so this issue finally gets some attention. Might need validation of already shipped code, who knows.
Best regards,
Marvin
> On 16. Dec 2022, at 20:54, Pedro Falcato <pedro.falcato@gmail.com> wrote:
>
>
> PS: it's worth noting that at this moment in time, due to this, the CLANG toolchains are very broken as they break the UEFI spec and are silently incompatible with modules compiled in both GCC and MSVC.
>
> Fixing this should be top priority.
>
> Pedro
[-- Attachment #2: Type: text/html, Size: 1417 bytes --]
next prev parent reply other threads:[~2022-12-16 20:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17315DF115C9EFAB.15628@groups.io>
2022-12-16 19:54 ` [edk2-devel] [PATCH 1/1] BaseTools: Fix IA32 UINT64 alignment for CLANG toolchains Pedro Falcato
2022-12-16 20:08 ` Marvin Häuser [this message]
2022-12-16 21:19 ` Michael D Kinney
2022-12-16 19:50 Pedro Falcato
2022-12-16 21:18 ` [edk2-devel] " Michael D Kinney
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=FC988F12-BC7C-4C99-8EA9-E9B5DE6F7313@posteo.de \
--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