From: Anshuman Khandual <anshuman.khandual@arm.com>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Build warning on drivers/acpi/tables.c:399
Date: Wed, 23 Apr 2025 12:52:26 +0530 [thread overview]
Message-ID: <edf62d1b-54c0-4e03-96fa-08048b258bfd@arm.com> (raw)
Hello,
Getting the following build warning with native arm64 gcc (Debian 10.2.1-6) 10.2.1
20210110 and with arm64 cross compiler as well.
drivers/acpi/tables.c:399:1: warning: ‘nonstring’ attribute ignored on objects of type ‘const char[][4]’ [-Wattributes]
399 | static const char table_sigs[][ACPI_NAMESEG_SIZE] __initconst __nonstring = {
| ^~~~~~
This is caused by a recent commit 4b4bd8c50f48 ("gcc-15: acpi: sprinkle random
'__nonstring' crumbles around"). Should that __nonstring attribute for table_sigsp[][]
be dropped off ? Apparently __nonstring attribute only applies for character arrays but
not applicable for arrays of character arrays.
- Anshuman
reply other threads:[~2025-04-23 7:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=edf62d1b-54c0-4e03-96fa-08048b258bfd@arm.com \
--to=anshuman.khandual@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=torvalds@linux-foundation.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 NNTP newsgroup(s).