https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108770

--- Comment #8 from Andrew Teylu <andrew.teylu at vector dot com> ---
> and also add the new option on top.

Doesn't the new option just cause gcc to elucidate the existing warning a bit
more?

I think, even if gcc tries to explain a bit more, the diagnostic is still
spurious.

Reply via email to