Closed seghcder closed 3 years ago
In theory, GCC should detect the 0-assignment in the next line and silence the warning. However, this part of GCC seems to be buggy and not always sees the 0-assignment.
Related: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87028
Adding superfluous parenthesis suppresses the warning. I added that.
Currently using GCC10 on Fedora32, however I believe this warning was added in GCC8
Nothing critical - still compiling and working it seems.
Full version
gcc version 10.2.1 20200723 (Red Hat 10.2.1-1) (GCC)
Thanks!