From: "Arnd Bergmann" <arnd@arndb.de>
To: "Marco Elver" <elver@google.com>,
"Miguel Ojeda" <miguel.ojeda.sandonis@gmail.com>
Cc: kasan-dev@googlegroups.com, linux-kernel@vger.kernel.org,
"Miguel Ojeda" <ojeda@kernel.org>,
"Dmitry Vyukov" <dvyukov@google.com>,
"Nathan Chancellor" <nathan@kernel.org>,
llvm@lists.linux.dev
Subject: Re: [PATCH 1/2] Compiler Attributes: Add __access macro
Date: Tue, 21 Apr 2026 21:30:17 +0200 [thread overview]
Message-ID: <63e461c3-2d8e-47c0-9901-34b53e53f22b@app.fastmail.com> (raw)
In-Reply-To: <CANpmjNPiyXdQnEXw=YbCrj4R5+8CvzNPX+C4gNaqW0Kjj2-k5A@mail.gmail.com>
On Tue, Apr 21, 2026, at 21:20, Marco Elver wrote:
> On Tue, 21 Apr 2026 at 21:15, Miguel Ojeda
> <miguel.ojeda.sandonis@gmail.com> wrote:
>>
>> On Tue, Apr 21, 2026 at 9:04 PM Marco Elver <elver@google.com> wrote:
>> >
>> > Add support for the `__access__` attribute, which is supported since gcc
>> > >= 11 but not currently supported by clang.
>>
>> > + * Optional: only supported since gcc >= 11
>>
>> From a quick try in Compiler Explorer, it seems GCC recognizes it
>> starting with GCC 10 rather than 11. It also seems to be in the docs.
>> Is there a reason for the 11?
>
> Oh, will fix. In the original report by Arnd we somehow concluded it
> was 11, but I guess I should double check such things. :-)
gcc-10 knows the 'access' attribute, but not the 'none' variant:
echo 'int f(void *p) __attribute__((access(none, 1)));' | /home/arnd/cross/arm64/gcc-10.5.0-nolibc/aarch64-linux/bin/aarch64-linux-gcc -xc - -o /dev/null -c
<stdin>:1:1: error: attribute 'access' invalid mode 'none'; expected one of 'read_only', 'read_write', or 'write_only'
Arnd
next prev parent reply other threads:[~2026-04-21 19:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-21 19:03 Marco Elver
2026-04-21 19:03 ` [PATCH 2/2] kcsan: Silence -Wmaybe-uninitialized when calling __kcsan_check_access() Marco Elver
2026-04-21 19:15 ` [PATCH 1/2] Compiler Attributes: Add __access macro Miguel Ojeda
2026-04-21 19:20 ` Marco Elver
2026-04-21 19:30 ` Arnd Bergmann [this message]
2026-04-21 19:35 ` Marco Elver
2026-04-22 10:25 ` Miguel Ojeda
2026-04-22 10:30 ` Miguel Ojeda
2026-04-22 13:22 ` David Laight
2026-04-22 5:50 ` Nathan Chancellor
2026-04-22 10:01 ` David Laight
2026-04-22 10:20 ` Marco Elver
2026-04-22 13:06 ` Marco Elver
2026-04-22 10:25 ` Miguel Ojeda
2026-04-22 13:02 ` David Laight
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=63e461c3-2d8e-47c0-9901-34b53e53f22b@app.fastmail.com \
--to=arnd@arndb.de \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=nathan@kernel.org \
--cc=ojeda@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®