[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <10569f4d724e57b63c5481b59bfaf8a8@smtp.hushmail.com>
Date: Sun, 27 Oct 2013 23:02:14 +0100
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: Compile john in Windows 64 bits
On 2013-10-27 22:50, magnum wrote:
> Solar,
>
> I added ALIGN_FIX support in x86-64.S for Dhiru to try out (he has added
> a mingw64 target now and NT crashes). But I don't quite get how it's
> supposed to work:
>
> #define DO_ALIGN(log) .align log; .space ALIGN_FIX
>
> So if we get an unaligned address, 8 bytes space are added and we're
> set. But what if we happened to get an aligned address in the first
> place? Then we will *become* unaligned, no?
I found some ancient (2008) information in list archives. Apparently
ALIGN_FIX is to be manually enabled on "unlucky builds" which pretty
much explains it. I still wonder if we could not end up wanting the fix
for just parts of x86-64.S - what if one section happens to be aligned
and another happens not to?
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.
