From: Nathan Chancellor <nathan@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: kernel test robot <lkp@intel.com>,
Nikunj A Dadhania <nikunj@amd.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [tip:x86/urgent 1/1] arch/x86/coco/sev/core.c:2170:30: warning: variable 'dummy' set but not used
Date: Wed, 2 Jul 2025 14:02:54 -0700 [thread overview]
Message-ID: <20250702210254.GA3996668@ax162> (raw)
In-Reply-To: <20250701152953.GCaGP-8bWPmRWI10Ec@fat_crate.local>
On Tue, Jul 01, 2025 at 05:29:53PM +0200, Borislav Petkov wrote:
> On Tue, Jul 01, 2025 at 08:06:44AM -0700, Nathan Chancellor wrote:
> > Citation needed. This reproduces with Clang 15 (earliest supported on
> > x86 now), Clang 19, and GCC 15 for me. Were you missing W=1?
>
> Nope.
>
> $ git checkout -b test 4a35d2b5254af89595fd90dae9ee0c8f990a148d
> Switched to a new branch 'test'
> $ make CC=clang-19 HOSTCC=clang-19 W=1 arch/x86/coco/sev/core.o
> ...
> LINK /mnt/kernel/kernel/linux/tools/objtool/objtool
> CC arch/x86/coco/sev/core.o
> $ clang-19 --version
> Debian clang version 19.1.7 (1+b1)
> Target: x86_64-pc-linux-gnu
> Thread model: posix
> InstalledDir: /usr/lib/llvm-19/bin
Spooky, same SHA, build command, and configuration from this thread with
Debian clang version 19.1.7 (3+b1)
Target: x86_64-pc-linux-gnu
Thread model: posix
InstalledDir: /usr/lib/llvm-19/bin
from unstable Debian (since it is what I base on for my Debian
development container) shows it for me... Can't imagine the two Debian
patch levels would have caused anything here but it is probably not
worth thinking too much more about since it is already resolved.
Cheers,
Nathan
prev parent reply other threads:[~2025-07-02 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 18:43 [tip:x86/urgent 1/1] arch/x86/coco/sev/core.c:2170:30: warning: variable 'dummy' set but not used kernel test robot
2025-06-30 19:27 ` Borislav Petkov
2025-07-01 15:06 ` Nathan Chancellor
2025-07-01 15:29 ` Borislav Petkov
2025-07-02 21:02 ` 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=20250702210254.GA3996668@ax162 \
--to=nathan@kernel.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=nikunj@amd.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.