Comment 1 for bug 1837329

I found the gcc bugzilla thread. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425

It is weird that optimization affects the warning?
I was hoping the `(void)` would get rid of it for just this case.

You can close if you believe the optimization should affect the warnings given. Probably the pass to report it is not executed at level 0.