https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86621
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Yes, but I certainly disagree with that, especially enabling a code-style warning by default. tree-vect-slp.c uses alloca 3 times, the warning is only in one spot, all of them are bound, because the vectorizer will not allow excessively large group sizes. I fail to see why people would need to add workarounds for this warnings, unless they want to enable it manually and have as a code style that all alloca calls must have a clearly visible (to the compiler) bound. If this triggers on gcc itself, it will trigger on many other programs. Unbound alloca isn't always a security issue, sure, there are projects that you want to make sure it never happens there, like glibc, but I think that is already explicitly enabling the warning.
