From: Jon Mason <jdmason@kudzu.us>
To: meta-arm@lists.yoctoproject.org, Jon Mason <jon.mason@arm.com>
Subject: Re: [PATCH] arm/optee: disable clang due to breakage
Date: Mon, 18 Mar 2024 14:25:37 -0400 [thread overview]
Message-ID: <171078633830.3024366.10015918426766532621.b4-ty@arm.com> (raw)
In-Reply-To: <20240318023558.85348-1-jon.mason@arm.com>
On Sun, 17 Mar 2024 22:35:58 -0400, Jon Mason wrote:
> With clang 18, optee-os no longer compiles cleanly. It is now seeing:
>
> | In file included from core/arch/arm/kernel/vfp.c:6:
> | In file included from core/arch/arm/include/arm.h:131:
> | core/arch/arm/include/arm64.h:436:1: error: expected readable system
> register
> | 436 | DEFINE_U32_REG_READWRITE_FUNCS(fpcr)
> | | ^
> | core/arch/arm/include/arm64.h:417:3: note: expanded from macro
> 'DEFINE_U32_REG_READWRITE_FUNCS'
> | 417 | DEFINE_U32_REG_READ_FUNC(reg) \
> | | ^
> | core/arch/arm/include/arm64.h:411:3: note: expanded from macro
> 'DEFINE_U32_REG_READ_FUNC'
> | 411 | DEFINE_REG_READ_FUNC_(reg, uint32_t, reg)
> | | ^
> | core/arch/arm/include/arm64.h:398:15: note: expanded from macro
> 'DEFINE_REG_READ_FUNC_'
> | 398 | asm volatile("mrs %0, " #asmreg : "=r" (val64));
> \
> | | ^
> | <inline asm>:1:10: note: instantiated into assembly here
> | 1 | mrs x8, fpcr
> | | ^
>
> [...]
Applied, thanks!
[1/1] arm/optee: disable clang due to breakage
commit: 67901eb5cbb774f5eac69374ee75b6dddac893c6
Best regards,
--
Jon Mason <jon.mason@arm.com>
prev parent reply other threads:[~2024-03-18 18:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 2:35 [PATCH] arm/optee: disable clang due to breakage Jon Mason
2024-03-18 18:25 ` Jon Mason [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=171078633830.3024366.10015918426766532621.b4-ty@arm.com \
--to=jdmason@kudzu.us \
--cc=jon.mason@arm.com \
--cc=meta-arm@lists.yoctoproject.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).