[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071011105806.GA28862@Chamillionaire.breakpoint.cc>
Date: Thu, 11 Oct 2007 12:58:06 +0200
From: Sebastian Siewior <netdev@...breakpoint.cc>
To: David Miller <davem@...emloft.net>
Cc: socketcan@...tkopp.net, herbert@...dor.apana.org.au,
netdev@...r.kernel.org
Subject: Re: authenc compile warnings in current net-2.6.24
* David Miller | 2007-10-10 16:25:28 [-0700]:
>From: Sebastian Siewior <netdev@...breakpoint.cc>
>Date: Wed, 10 Oct 2007 21:53:37 +0200
>
>> * Oliver Hartkopp | 2007-10-10 19:53:53 [+0200]:
>>
>> > CC [M] crypto/authenc.o
>> > crypto/authenc.c: In function ?crypto_authenc_hash?:
>> > crypto/authenc.c:88: warning: ?cryptlen? may be used uninitialized in this
>> > function
>> > crypto/authenc.c:87: warning: ?dst? may be used uninitialized in this
>> > function
>> > crypto/authenc.c: In function ?crypto_authenc_decrypt?:
>> > crypto/authenc.c:163: warning: ?cryptlen? may be used uninitialized in this
>> > function
>> > crypto/authenc.c:163: note: ?cryptlen? was declared here
>> > crypto/authenc.c:162: warning: ?src? may be used uninitialized in this
>> > function
>> > crypto/authenc.c:162: note: ?src? was declared here
>> >
>> > do you already know these warnings?
>>
>> Those warnings are looking like a compiler bug to me.
>
>To be honest I don't know of any compiler which commits enough
>flow variable analysis to support doing %100 accurate warnings
>in situations like this.
gcc (GCC) 4.1.2 (Gentoo 4.1.2) did not produce any warnings in this
case.
>Since the compiler is unlikely to do so, I think we should fix
>it somehow because useless warnings just distract.
sure.
Sebastian
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists