From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Sebastian Siewior <netdev@ml.breakpoint.cc>, netdev@vger.kernel.org
Subject: Re: authenc compile warnings in current net-2.6.24
Date: Thu, 11 Oct 2007 18:38:35 +0200 [thread overview]
Message-ID: <470E518B.1020006@hartkopp.net> (raw)
In-Reply-To: <20071011105806.GA28862@Chamillionaire.breakpoint.cc>
Sebastian Siewior wrote:
> * David Miller | 2007-10-10 16:25:28 [-0700]:
>
>
>> From: Sebastian Siewior <netdev@ml.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.
>
>
Hi Sebasian,
my gcc was the lastest Debian unstable one:
gcc -v
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v
--enable-languages=c,c++,fortran,objc,obj-c++,treelang --prefix=/usr
--enable-shared --with-system-zlib --libexecdir=/usr/lib
--without-included-gettext --enable-threads=posix --enable-nls
--with-gxx-include-dir=/usr/include/c++/4.2 --program-suffix=-4.2
--enable-clocale=gnu --enable-libstdcxx-debug --enable-mpfr
--enable-targets=all --disable-werror --enable-checking=release
--build=i486-linux-gnu --host=i486-linux-gnu --target=i486-linux-gnu
Thread model: posix
gcc version 4.2.1 (Debian 4.2.1-5)
Regards,
Oliver
next prev parent reply other threads:[~2007-10-11 16:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 17:53 authenc compile warnings in current net-2.6.24 Oliver Hartkopp
2007-10-10 19:53 ` Sebastian Siewior
2007-10-10 23:25 ` David Miller
2007-10-11 3:23 ` Herbert Xu
2007-10-11 3:26 ` Herbert Xu
2007-10-11 10:58 ` Sebastian Siewior
2007-10-11 16:38 ` Oliver Hartkopp [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-12 6:15 Oliver Hartkopp
2007-10-12 10:18 ` Herbert Xu
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=470E518B.1020006@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=netdev@ml.breakpoint.cc \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).