From: Daniel Borkmann <daniel@iogearbox•net>
To: Stephen Hemminger <stephen@networkplumber•org>
Cc: Phil Sutter <phil@nwl•cc>, netdev@vger•kernel.org
Subject: Re: [PATCH iproute2] ip, route: fix minor compile warning
Date: Fri, 18 Dec 2015 10:18:23 +0100 [thread overview]
Message-ID: <5673CF5F.1060806@iogearbox.net> (raw)
In-Reply-To: <20151217171203.723b4d16@xeon-e3>
On 12/18/2015 02:12 AM, Stephen Hemminger wrote:
> On Mon, 14 Dec 2015 16:53:20 +0100
> Daniel Borkmann <daniel@iogearbox•net> wrote:
>
>> On 12/14/2015 04:51 PM, Phil Sutter wrote:
>>> On Mon, Dec 14, 2015 at 04:34:29PM +0100, Daniel Borkmann wrote:
>>>> Seems like gcc (4.8.3) doesn't catch this false positive, triggering
>>>> after 0f7543322c5f ("route: ignore RTAX_HOPLIMIT of value -1"):
>>>>
>>>> iproute.c: In function 'print_route':
>>>> iproute.c:301:12: warning: 'val' may be used uninitialized in this function [-Wmaybe-uninitialized]
>>>> features &= ~RTAX_FEATURE_ECN;
>>>> ^
>>>> iproute.c:575:10: note: 'val' was declared here
>>>> __u32 val;
>>>> ^
>>>> So just shut it up by initializing to 0.
>>>
>>> Hmm. Interestingly, my patch shouldn't have changed anything relevant
>>> for gcc's decision. OTOH, I don't see a warning using gcc-4.9.3.
>>
>> If I revert it, the warning is gone for me ;) perhaps some heuristic issue
>> with that gcc version.
>>
>> Cheers,
>> Daniel
>
> I don't see this warning on current master with gcc 4.9.2.
Well, in the commit message I wrote 4.8.3 ... but I don't mind if we drop it, sure.
prev parent reply other threads:[~2015-12-18 9:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 15:34 [PATCH iproute2] ip, route: fix minor compile warning Daniel Borkmann
2015-12-14 15:51 ` Phil Sutter
2015-12-14 15:53 ` Daniel Borkmann
2015-12-18 1:12 ` Stephen Hemminger
2015-12-18 9:18 ` Daniel Borkmann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5673CF5F.1060806@iogearbox.net \
--to=daniel@iogearbox$(echo .)net \
--cc=netdev@vger$(echo .)kernel.org \
--cc=phil@nwl$(echo .)cc \
--cc=stephen@networkplumber$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox