Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 21 Feb 2012 21:18:42 +0400
From: Solar Designer <>
Subject: Re: Compile john in Windows 64 bits

Jim, Alain -

On Tue, Feb 21, 2012 at 10:59:05AM -0600, jfoug wrote:
> For 32 bit, mingw .o files can be used perfectly fine by VC.  I have not
> proceeded to try to get mingw64 working properly with VC's 64 bit stuff.
> However, I would bet it is built to work properly.
> So, the 'hard' objects can be done with mingw64 (any .S files, the DES
> stuff, etc).  Then the rest of the files can be built with VC, and have VC
> link the previously built .o files.
> For some of the .S files, I had to make parameter marshaling functions (on
> the 32 bit side).  I would image something similar may be required for doing
> any GAS porting to VC.

What's the point in using mingw + VC vs. using mingw only?  Is that
solely because we expect VC to optimize better than gcc?  If so, I'd
prefer that we arrive at a working Win64 mingw-only make target first -
that anyone could use without having a VC license.

Thanks for working on this!


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.