[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2911b0d04156bc4a7d9fac7a9775066e@smtp.hushmail.com>
Date: Wed, 13 Jun 2012 22:49:00 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Compiler warnings (was: Re: GPU fixes)
On 2012-06-13 22:32, Lukas Odzioba wrote:
> 2012/6/13 magnum<john.magnum@...hmail.com>:
>> We still get several screenfuls of compiler warnings when building, mostly
>> from wpapsk. Do you intend to fix this? Otherwise I'll do it. I am fed up
>> with them. Also, additional warnings in other places were introduced by your
>> latest GPU patch (not the device list one).
>
> What you've sent me was complete list? I assume that they are from 64bit build.
> I fixed some..: that's what's left:
> 32bit
> http://ideone.com/RMDPT
> http://ideone.com/CuIP0
Thanks, yes it was a complete list from gcc 4.6.3. Some of these were
new to me, some others (NT and mscash1) I too saw today when using gcc
4.4. These warnings tend to change with compiler version. I'll have a
look at RAR and the others.
Jim, the NT and mscash1 warnings shown in the links above are from your
Sparc fixes. The weird things are:
1) I just can not understand how they break aliasing rules (we cast to
shorter)
2) In NS_fmt_plug.c, *exactly* the same type of code is used, yet it
does not produce warnings. Why?!
magnum
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
