[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANiq72nZNU-x_8ONmtzainxDUMedFT+FHww1xu9Ho07gxfAD9w@mail.gmail.com>
Date: Thu, 4 May 2023 20:27:32 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: 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 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.
(I can change it on my side if you prefer)
Thanks!
Cheers,
Miguel
Powered by blists - more mailing lists