On Thu, Feb 06, 2025 at 10:52:18AM -0800, Kees Cook wrote:
> On Thu, Feb 06, 2025 at 08:45:41PM +0200, Andy Shevchenko wrote:
> > On Thu, Feb 6, 2025 at 8:44 PM Miguel Ojeda
> > wrote:
> > > On Thu, Feb 6, 2025 at 7:42 PM Andy Shevchenko
> > > wrote:
> > > >
> > > > What's the minimum Clang versi
On Thu, Feb 06, 2025 at 08:45:41PM +0200, Andy Shevchenko wrote:
> On Thu, Feb 6, 2025 at 8:44 PM Miguel Ojeda
> wrote:
> >
> > On Thu, Feb 6, 2025 at 7:42 PM Andy Shevchenko
> > wrote:
> > >
> > > What's the minimum Clang version we build kernel with? 12?
> >
> > 13.0.1 for most architectures ac
On Thu, Feb 6, 2025 at 8:44 PM Miguel Ojeda
wrote:
>
> On Thu, Feb 6, 2025 at 7:42 PM Andy Shevchenko
> wrote:
> >
> > What's the minimum Clang version we build kernel with? 12?
>
> 13.0.1 for most architectures according to `scripts/min-tool-version.sh`.
Okay, does it mean 13 has no such a bug?
On Thu, Feb 6, 2025 at 7:42 PM Andy Shevchenko
wrote:
>
> What's the minimum Clang version we build kernel with? 12?
13.0.1 for most architectures according to `scripts/min-tool-version.sh`.
Cheers,
Miguel
On Thu, Feb 6, 2025 at 8:11 PM Kees Cook wrote:
>
> Work around a Clang 14 bug by switching to ARRAY_SIZE() (with the
> added benefit of explicitly checking for char array arguments) in
> memtostr*/strtomem*().
What's the minimum Clang version we build kernel with? 12?
--
With Best Regards,
And
