On Wed, 9 Apr 2025 at 05:20, Mark Brown <broo...@kernel.org> wrote:
>
> Note that the patch is only disabling for build coverage builds where
> the resulting binaries generally aren't going to actually be run.
Well, there's a reason we do build coverage - we also want to test
that the non-build coverage case builds.
And it's not actually obvious that it does - it's in fact rather
likely that the gcc plugin is broken in general, and it just so
happens that it's the build bots that find it.
Which is why I honestly would prefer to just disable the plugins in general.
Because the problem is the plugin, not the build coverage.
Linus
