From: Nathan Chancellor <nathan@kernel.org>
To: ci_notify@linaro.org
Cc: Mubashar Ahmad <mubashar.ahmad@arm.com>, llvm@lists.linux.dev
Subject: Re: [TCWG CI] Regression caused by llvm: [Clang][AArch64][ARM] Unaligned Access Warning Added
Date: Sat, 22 Jan 2022 19:17:45 -0700 [thread overview]
Message-ID: <Yey6yY6hmj+Fb2L0@dev-arch.archlinux-ax161> (raw)
In-Reply-To: <1454838115.14607.1642854713913@jenkins.jenkins>
On Sat, Jan 22, 2022 at 12:31:52PM +0000, ci_notify@linaro.org wrote:
> [TCWG CI] Regression caused by llvm: [Clang][AArch64][ARM] Unaligned Access Warning Added:
> commit 35737df4dcd28534bd3090157c224c19b501278a
> Author: Mubashar Ahmad <mubashar.ahmad@arm.com>
>
> [Clang][AArch64][ARM] Unaligned Access Warning Added
>
> Results regressed to
> # reset_artifacts:
> -10
> # build_abe binutils:
> -9
> # build_llvm:
> -5
> # build_abe qemu:
> -2
> # linux_n_obj:
> 20623
> # First few build errors in logs:
> # 00:03:03 ./include/linux/tpm.h:288:2: error: field within 'struct tpm_header' is less aligned than 'union tpm_header::(anonymous at ./include/linux/tpm.h:288:2)' and is usually due to 'struct tpm_header' being packed, which can lead to unaligned accesses [-Werror,-Wunaligned-access]
> # 00:03:03 make[3]: *** [scripts/Makefile.build:277: security/keys/encrypted-keys/encrypted.o] Error 1
> # 00:03:03 make[2]: *** [scripts/Makefile.build:540: security/keys/encrypted-keys] Error 2
> # 00:03:05 ./include/linux/tpm.h:288:2: error: field within 'struct tpm_header' is less aligned than 'union tpm_header::(anonymous at ./include/linux/tpm.h:288:2)' and is usually due to 'struct tpm_header' being packed, which can lead to unaligned accesses [-Werror,-Wunaligned-access]
> # 00:03:05 make[3]: *** [scripts/Makefile.build:277: security/keys/trusted-keys/trusted_core.o] Error 1
> # 00:03:06 ./include/linux/tpm.h:288:2: error: field within 'struct tpm_header' is less aligned than 'union tpm_header::(anonymous at ./include/linux/tpm.h:288:2)' and is usually due to 'struct tpm_header' being packed, which can lead to unaligned accesses [-Werror,-Wunaligned-access]
> # 00:03:06 make[3]: *** [scripts/Makefile.build:277: security/keys/trusted-keys/trusted_tpm1.o] Error 1
> # 00:03:07 ./include/linux/tpm.h:288:2: error: field within 'struct tpm_header' is less aligned than 'union tpm_header::(anonymous at ./include/linux/tpm.h:288:2)' and is usually due to 'struct tpm_header' being packed, which can lead to unaligned accesses [-Werror,-Wunaligned-access]
> # 00:03:07 make[3]: *** [scripts/Makefile.build:277: security/keys/trusted-keys/trusted_tpm2.o] Error 1
> # 00:03:08 ./include/linux/tpm.h:288:2: error: field within 'struct tpm_header' is less aligned than 'union tpm_header::(anonymous at ./include/linux/tpm.h:288:2)' and is usually due to 'struct tpm_header' being packed, which can lead to unaligned accesses [-Werror,-Wunaligned-access]
Thank you a lot for the report. I have opened an issue on GitHub for us
to track this new warning:
https://github.com/ClangBuiltLinux/linux/issues/1569
Cheers,
Nathan
prev parent reply other threads:[~2022-01-23 2:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 12:31 [TCWG CI] Regression caused by llvm: [Clang][AArch64][ARM] Unaligned Access Warning Added ci_notify
2022-01-23 2:17 ` Nathan Chancellor [this message]
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=Yey6yY6hmj+Fb2L0@dev-arch.archlinux-ax161 \
--to=nathan@kernel.org \
--cc=ci_notify@linaro.org \
--cc=llvm@lists.linux.dev \
--cc=mubashar.ahmad@arm.com \
/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