[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f5f0a117a65fbf765bf3a4cfa5e8a994@smtp.hushmail.com>
Date: Fri, 16 Nov 2012 00:55:07 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Out of options flags
On 16 Nov, 2012, at 0:44 , Solar Designer <solar@...nwall.com> wrote:
> On Thu, Nov 15, 2012 at 11:11:14PM +0100, magnum wrote:
>> We have been out of options flags for some time now and I need some more. Are you OK with me changing the typedef of opt_flags to ARCH_WORD_64 in Jumbo and make the other necessary changes to support this? Or do you have some better suggestion?
>
> Going 64-bit for the option flags in jumbo sounds right to me. While I
> do hope to come up with a better solution, I don't readily have one and
> when I do I think it'd be best to implement it in core first.
>
> When you implement this change, can you also move all of jumbo-specific
> flags (those already allocated) to the high 32 bits (newly added),
> thereby leaving the low 32 bits to core (for a few new options to be
> added in core before we run into the same issue there)?
Sounds like a good idea, will do.
Thanks,
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.
