It had been fixed in development branch before, and the fix was intended to silence a warning at that time. Because of that, the commit log doesn't directly address it's a bug.
Now with GCC 5, we have a concrete example which hits the bug. Namely, OpenPGP-compliant valid signature might be
regected.
This bug is fixed in upstream.
GnuPG 1.4: git.gnupg. org/cgi- bin/gitweb. cgi?p=gnupg. git;a=commit; h=6db18e29eb81b 37ed6feb592add7 7d492c60fc35
http://
GnuPG 2.0: git.gnupg. org/cgi- bin/gitweb. cgi?p=gnupg. git;a=commit; h=b1653a4083b91 cfa85d90f59612f a1c3f4d51778
http://
It had been fixed in development branch before, and the fix was intended to silence a warning at that time. Because of that, the commit log doesn't directly address it's a bug.
Now with GCC 5, we have a concrete example which hits the bug. Namely, OpenPGP-compliant valid signature might be
regected.