[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9d3c8d52bf68abc2dcb953d405d6d3f7@smtp.hushmail.com>
Date: Sun, 27 Jan 2013 18:43:10 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: krb5-23 or wow bug (or what?)
On 27 Jan, 2013, at 17:39 , Solar Designer <solar@...nwall.com> wrote:
> On Sun, Jan 27, 2013 at 05:03:29PM +0100, magnum wrote:
>> Ah, yes. I never got around the alloca problem so I use gcc-4.7 from homebrew.
>
> I think we shouldn't be using alloca(). Luckily, there are very few
> uses - we should simply get rid of them.
For portability reasons, or some other reason as well? There are also some uses of variable-size arrays, which boils down to the same thing. These are harder to just grep out but I can easily list them trying to do OMP with Apple's gcc :)
How do we get rid of them? Using stack arrays of maximum size that will ever be needed?
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.
