From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Saket Dumbre <saket.dumbre@intel.com>,
Robert Moore <robert.moore@intel.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
linux-acpi@vger.kernel.org, acpica-devel@lists.linux.dev
Subject: Re: ACPICA compilation error on x86_64_defconfig (W=1 build)
Date: Mon, 7 Apr 2025 21:51:14 +0300 [thread overview]
Message-ID: <Z_Qeot7pps5Q4vx7@smile.fi.intel.com> (raw)
In-Reply-To: <CAJZ5v0j2Y3vPZhUGJmcWzn6esg9zv5an0KPEN4QfQuyGrd5=YQ@mail.gmail.com>
On Mon, Apr 07, 2025 at 08:49:41PM +0200, Rafael J. Wysocki wrote:
> On Mon, Apr 7, 2025 at 8:47 PM Andy Shevchenko
> <andriy.shevchenko@intel.com> wrote:
> >
> > v6.15-rc1 (but seems older should also be problematic) fails to compile by
> > Clang 19 with `make W=1`.
> >
> > CC drivers/acpi/acpica/nsaccess.o
> > drivers/acpi/acpica/nsaccess.c:295:6: error: variable 'num_carats' set but not used [-Werror,-Wunused-but-set-variable]
> > 295 | u32 num_carats;
> > | ^
> > 1 error generated.
> >
> > I looked briefly in the code and I have no idea how to fix this, as probably
> > __maybe_unused not an option for ACPICA. Hence this report.
> >
> > Note, the in-tree defconfig is in use:
> >
> > git checkout v6.15-rc1
> > make x86_64_defconfig
> > make W=1
Since it's a clang, this should have also something like LLVM=1.
> > should trigger it.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-04-07 18:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 18:47 ACPICA compilation error on x86_64_defconfig (W=1 build) Andy Shevchenko
2025-04-07 18:49 ` Rafael J. Wysocki
2025-04-07 18:51 ` Andy Shevchenko [this message]
[not found] ` <LV8PR11MB86980990221C597E01BAEB7980B52@LV8PR11MB8698.namprd11.prod.outlook.com>
[not found] ` <LV8PR11MB8698978FFF89ACBEF253667680B52@LV8PR11MB8698.namprd11.prod.outlook.com>
2025-04-09 11:24 ` Shevchenko, Andriy
2025-04-09 14:00 ` Shevchenko, Andriy
2025-04-09 14:07 ` Rafael J. Wysocki
2025-04-09 14:15 ` Shevchenko, Andriy
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=Z_Qeot7pps5Q4vx7@smile.fi.intel.com \
--to=andriy.shevchenko@intel.com \
--cc=acpica-devel@lists.linux.dev \
--cc=linux-acpi@vger.kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=robert.moore@intel.com \
--cc=saket.dumbre@intel.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