All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: Robert Moore <robert.moore@intel.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Cc: linux-acpi@vger.kernel.org, acpica-devel@lists.linux.dev
Subject: ACPICA compilation error on x86_64_defconfig (W=1 build)
Date: Mon, 7 Apr 2025 21:47:47 +0300	[thread overview]
Message-ID: <Z_Qd0x6bLSQjJ7Rw@smile.fi.intel.com> (raw)

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

should trigger it.

-- 
With Best Regards,
Andy Shevchenko



             reply	other threads:[~2025-04-07 18:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-07 18:47 Andy Shevchenko [this message]
2025-04-07 18:49 ` ACPICA compilation error on x86_64_defconfig (W=1 build) Rafael J. Wysocki
2025-04-07 18:51   ` Andy Shevchenko
     [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_Qd0x6bLSQjJ7Rw@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=robert.moore@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 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.