public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ross Burton" <ross@burtonini.com>
To: devel@edk2.groups.io
Subject: MdeModulePkg fails to build with latest clang 14
Date: Mon, 21 Feb 2022 08:28:01 -0800	[thread overview]
Message-ID: <cZU0.1645460881414234925.6Xte@groups.io> (raw)

When building edk2 202111 with clang 14 I get the following errors:

edk2/MdeModulePkg/Include/Guid/ExtendedFirmwarePerformance.h:78:47: error: field Guid within 'FPDT_GUID_EVENT_RECORD' is less aligned than 'EFI_GUID' (aka 'GUID') and is usually due to 'FPDT_GUID_EVENT_RECORD' being packed, which can lead to unaligned accesses [-Werror,-Wunaligned-access]
  EFI_GUID                                    Guid;
                                              ^
edk2/MdeModulePkg/Include/Guid/ExtendedFirmwarePerformance.h:173:47: error: field Guid within 'FPDT_GUID_QWORD_EVENT_RECORD' is less aligned than 'EFI_GUID' (aka 'GUID') and is usually due to 'FPDT_GUID_QWORD_EVENT_RECORD' being packed, which can lead to unaligned accesses [-Werror,-Wunaligned-access]
  EFI_GUID                                    Guid;
                                              ^
edk2/MdeModulePkg/Include/Guid/ExtendedFirmwarePerformance.h:105:47: error: field Guid within 'FPDT_DYNAMIC_STRING_EVENT_RECORD' is less aligned than 'EFI_GUID' (aka 'GUID') and is usually due to 'FPDT_DYNAMIC_STRING_EVENT_RECORD' being packed, which can lead to unaligned accesses [-Werror,-Wunaligned-access]
  EFI_GUID                                    Guid;
                                              ^

Has this been fixed in master?

Ross

             reply	other threads:[~2022-02-21 16:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21 16:28 Ross Burton [this message]
2022-02-22  1:55 ` 回复: [edk2-devel] MdeModulePkg fails to build with latest clang 14 gaoliming
2022-02-22 10:15   ` Ross Burton

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=cZU0.1645460881414234925.6Xte@groups.io \
    --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