[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: some gcc warnings
|
From: |
Paul Eggert |
|
Subject: |
Re: some gcc warnings |
|
Date: |
Thu, 4 May 2017 15:55:37 -0700 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.0 |
On 05/04/2017 03:24 PM, Bruno Haible wrote:
https://dev.gnupg.org/rCf17d50bbd31b1faa24af1e46c10bba845becf585
https://dev.gnupg.org/rCdfb4673da8ee52d95e0a62c9f49ca8599943f22e
But 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.