Uninitialized data warnings about qcbor HOT 3 CLOSED

Looks like gcc 10.2 has some warnings that 10.1 doesn't.

I don't think there are any real problems in QCBOR, but I will figure out a fix in the next few days.

Thanks for reporting!

from qcbor.

I've spent some time on this and so far can't replicate it and haven't got to the bottom of it.

When I try adding -Wmaybe-uninitialized for gcc-9, gcc-10 and gcc-11 on MacOS it tells me the warning flag doesn't exist. I've also tried llvm/clang.

I build with -Wall and -Wextra and that is supposed tot set -Wmaybe-uninitialized, but I don't get warnings.

I do not believe there are any actual problems with the code.

I will keep looking, but if you have any more info or such it might be helpful.

from qcbor.

Closing this because I can't reproduce it, no one else has turned this and the filer of this hasn't commented further.

from qcbor.