On Tue, Jan 18, 2022 at 01:20:40PM -0800, Kees Cook wrote: > I haven't been able to reproduce the specific cause of why GCC decided to > do the bounds checking, but it's not an unreasonable thing to check for, > just for robustness. Well, the commit message should explain this is to silence a compiler bug and maybe put some colour on what version(s) are actually buggy.. Jason
