On 05/04/2017 03:24 PM, Bruno Haible wrote:
https://dev.gnupg.org/rCf17d50bbd31b1faa24af1e46c10bba845becf585 https://dev.gnupg.org/rCdfb4673da8ee52d95e0a62c9f49ca8599943f22eBut this fix is only effective for GCC. How could a compiler-independent fix look like?
Why do we need a compiler-independent fix? The code itself is portable as-is, right? So the only reason the change is needed is to pacify GCC when its warnings are cranked up too high.
