[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <40D4BB7A-2583-45B9-B76A-E174CAC4B248@kernel.org>
Date: Thu, 04 May 2023 16:44:24 -0700
From: Kees Cook <kees@...nel.org>
To: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>,
Kees Cook <keescook@...omium.org>
CC: Miguel Ojeda <ojeda@...nel.org>, Bill Wendling <morbo@...gle.com>,
Qing Zhao <qing.zhao@...cle.com>,
"Gustavo A . R . Silva" <gustavoars@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Nathan Chancellor <nathan@...nel.org>,
Tom Rix <trix@...hat.com>, llvm@...ts.linux.dev,
linux-kernel@...r.kernel.org, linux-hardening@...r.kernel.org
Subject: Re: [PATCH] Compiler Attributes: Add __counted_by macro
On May 4, 2023 11:27:32 AM PDT, Miguel Ojeda <miguel.ojeda.sandonis@...il.com> wrote:
>On Thu, May 4, 2023 at 8:16 PM Kees Cook <keescook@...omium.org> wrote:
>>
>> + * Optional: future support coming in clang 17 and gcc 14
>
>Should we just say:
>
> Optional: only supported since clang >= 17
> Optional: only supported since gcc >= 14
>
>even if they are in the future? That way we avoid changing it later.
>If somebody asks, you already say it it is in the future the commit
>message, so it should be clear enough... :)
>
>And if the compilers end up not supporting it on those versions for
>some unexpected reason, well, we will need to fix the comment either
>way.
Yeah, fair point!
>
>(I can change it on my side if you prefer)
Sure, thanks! (But I'm happy to send a v2 if that's easier for you, too.)
-Kees
--
Kees Cook
Powered by blists - more mailing lists