From: "tianjia.zhang" <tianjia.zhang@linux.alibaba.com>
To: Nick Desaulniers <ndesaulniers@google.com>
Cc: "Marc Zyngier" <maz@kernel.org>,
"Oliver Upton" <oliver.upton@linux.dev>,
"Joey Gouly" <joey.gouly@arm.com>,
"Suzuki K Poulose" <suzuki.poulose@arm.com>,
"Zenghui Yu" <yuzenghui@huawei.com>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Bill Wendling" <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>,
"Pierre-Clément Tosi" <ptosi@google.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org, llvm@lists.linux.dev
Subject: Re: [PATCH] KVM: arm64: nVHE: gen-hyprel: Silent build warnings
Date: Mon, 14 Oct 2024 14:50:21 +0800 [thread overview]
Message-ID: <78a18ddd-4704-49ce-86b2-05693ac9b032@linux.alibaba.com> (raw)
In-Reply-To: <CAKwvOdnkTOjV_j6zGAkghgU0L_tLkb=8Nh3Qzvdb1N-tV61wag@mail.gmail.com>
Hi Nick,
On 10/10/24 11:23 PM, Nick Desaulniers wrote:
> On Thu, Oct 10, 2024 at 1:13 AM tianjia.zhang
> <tianjia.zhang@linux.alibaba.com> wrote:
>>
>>
>>
>> On 10/9/24 7:07 PM, Marc Zyngier wrote:
>>> On Wed, 09 Oct 2024 09:57:51 +0100,
>>> Tianjia Zhang <tianjia.zhang@linux.alibaba.com> wrote:
>>>>
>>>> This patch silent the some mismatch format build warnings
>>>> with clang, like:
>>>>
>>>> arch/arm64/kvm/hyp/nvhe/gen-hyprel.c:233:2: warning: format specifies
>>>> type 'unsigned long' but the argument has type 'Elf64_Off'
>>>> (aka 'unsigned long long') [-Wformat]
>>>> 233 | assert_ne(off, 0UL, "%lu");
>>>> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
>>>> | %llu
>>>> arch/arm64/kvm/hyp/nvhe/gen-hyprel.c:193:34: note: expanded from macro 'assert_ne'
>>>> 193 | #define assert_ne(lhs, rhs, fmt) assert_op(lhs, rhs, fmt, !=)
>>>> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>> arch/arm64/kvm/hyp/nvhe/gen-hyprel.c:188:19: note: expanded from macro 'assert_op'
>>>> 187 | " failed (lhs=" fmt ", rhs=" fmt \
>>>> | ~~~
>>>> 188 | ", line=%d)", _lhs, _rhs, __LINE__); \
>>>> | ^~~~
>>>> arch/arm64/kvm/hyp/nvhe/gen-hyprel.c:167:17: note: expanded from macro 'fatal_error'
>>>> 166 | fprintf(stderr, "error: %s: " fmt "\n", \
>>>> | ~~~
>>>> 167 | elf.path, ## __VA_ARGS__); \
>>>> | ^~~~~~~~~~~
>>>>
>>>> Signed-off-by: Tianjia Zhang <tianjia.zhang@linux.alibaba.com>
>>>
>>> I don't see these warnings. What version of LLVM are you using?
>>>
>>
>> I compiled the kernel on Apple Silicon M3 Pro in macOS 15.0.1, Maybe this is
>> a special scenario that is rarely used.
>
> Right, so I had an initial patch set for building the kernel from a
> MacOS host. I sent a v1, but didn't chase sending a v2 at the time
> because there didn't appear to be any interest.
>
> https://www.phoronix.com/news/Linux-Compile-On-macOS
>
> Since then, I saw a v2 or even a v3 fly by (I was cc'ed).
>
> One issue I recall building from MacOS was that MacOS does not have an
> <elf.h> (their object file format is not ELF, but Mach-O). I had to
> install some dependency through homebrew for that header.
>
> Just a guess but:
> Perhaps it defines Elf64_Off as a `unsigned long` incorrectly, and
> should be defining it as an `unsigned long long`. I'd check if that's
> the case and if so, Tianjia, you may want to report that issue on the
> thread where folks are reposting the MacOS host support.
>
Thanks for the information, great work, very useful attempt.
I have successfully compiled the latest 6.11 rc2 on macOS 15.0.1 Apple
Silicon M3 chip. It seems that compiling on this version of the kernel
is easier. I just added three header files, elf.h, byteswap.h and
endian.h, and add the missing definitions. In addition, I fixed
scriptsj/mod/file2alias.c as you did, and it compiled successfully
without encountering other exceptions. The dependent toolchains are
all installed through brew, include make, llvm and lld.
Cheers,
Tianjia
next prev parent reply other threads:[~2024-10-14 6:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-09 8:57 [PATCH] KVM: arm64: nVHE: gen-hyprel: Silent build warnings Tianjia Zhang
2024-10-09 11:07 ` Marc Zyngier
2024-10-10 8:12 ` tianjia.zhang
2024-10-10 13:03 ` Marc Zyngier
2024-10-14 6:31 ` tianjia.zhang
2024-10-10 15:23 ` Nick Desaulniers
2024-10-14 6:50 ` tianjia.zhang [this message]
2024-10-16 6:19 ` kernel test robot
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=78a18ddd-4704-49ce-86b2-05693ac9b032@linux.alibaba.com \
--to=tianjia.zhang@linux.alibaba.com \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--cc=justinstitt@google.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=maz@kernel.org \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=oliver.upton@linux.dev \
--cc=ptosi@google.com \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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;
as well as URLs for NNTP newsgroup(s).