[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: avoid new GCC-7-exposed warnings
From: |
Pádraig Brady |
Subject: |
Re: avoid new GCC-7-exposed warnings |
Date: |
Sat, 15 Oct 2016 10:55:59 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 |
On 15/10/16 05:47, Jim Meyering wrote:
> I tried to build the coreutils using very recent GCC 7, built from
> latest git, and encountered a few new warnings (errors when configured
> with --enable-gcc-warnings), so wrote the following to address them.
> With these, everything now compiles warning free:
All look good.
I had a similar idea to die() with errorx() at:
http://lists.gnu.org/archive/html/coreutils/2016-07/msg00038.html
It seems like die() would be good in more cases.
The two here:
http://git.sv.gnu.org/gitweb/?p=coreutils.git;a=commitdiff;h=558ce30
and the others noted by Bernhard:
http://lists.gnu.org/archive/html/coreutils/2016-07/msg00039.html
thanks!
Pádraig
- avoid new GCC-7-exposed warnings, Jim Meyering, 2016/10/15
- Re: avoid new GCC-7-exposed warnings,
Pádraig Brady <=
- Re: avoid new GCC-7-exposed warnings, Jim Meyering, 2016/10/15
- Re: avoid new GCC-7-exposed warnings, Pádraig Brady, 2016/10/15
- Re: avoid new GCC-7-exposed warnings, Pádraig Brady, 2016/10/15
- Re: avoid new GCC-7-exposed warnings, Jim Meyering, 2016/10/16
- Re: avoid new GCC-7-exposed warnings, Pádraig Brady, 2016/10/16
- Re: avoid new GCC-7-exposed warnings, Jim Meyering, 2016/10/16