Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <f54ed46a6c6ff731d3414294ce470a01@smtp.hushmail.com>
Date: Wed, 29 Aug 2012 20:00:56 +0200
From: magnum <john.magnum@...hmail.com>
To: john-users@...ts.openwall.com
Subject: Re: Questions about compiling for Optimal CPU  Performance

On 29 aug 2012, at 17:55, Brad Tilley <brad@...ystems.com> wrote:

>>> My older Intel Celeron CPU lists sse, sse2 and sse3 as supported in
>>> /proc/cpuinfo, should I make-x86-sse2 or make-x86-native when compiling
>>> jumbo-6? Or does the difference really matter?
>> 
>> You should probably use linux-x86-64i. If you run a 32-bit OS, you should
>> really ask yourself why.
> 
> You're joking, aren't you? Some CPUs are still 32-bit only or have 64-bit
> capability, but disable it (such as some Intel Atoms). So when asked why,
> that is the reason I sometimes use a 32-bit operating system and cannot
> use a 64-bit OS for those specific CPUs. You can understand that I hope.
> Not sure why this would be questioned... am I missing something? An inside
> joke only related to JtR perhaps?


Sorry, I thought all Celeron was 64-bit. Is that not the case? For a 32-bit build, linux-x86-sse2i is probably best, it uses intrinsics code precompiled with icc.

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.