Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 5 Jan 2012 03:11:47 +0400
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: gcc versions

On Thu, Jan 05, 2012 at 12:47:28AM +0400, Solar Designer wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51017#c5
> 
> 4.3.5 20100502 - 2950K c/s, 28229 bytes
> 4.3.6 20110626 - 2950K c/s, 28229 bytes
> 4.4.5 20100504 - 2697K c/s, 29764 bytes
> 4.4.7 20120103 - 2691K c/s, 29316 bytes
> 4.5.1 20100603 - 2729K c/s, 29203 bytes
> 4.5.4 20111229 - 2710K c/s, 29203 bytes
> 4.6.0 20100703 - 2133K c/s, 29911 bytes
> 4.6.0 20100807 - 2119K c/s, 29940 bytes
> 4.6.0 20100904 - 2142K c/s, 29848 bytes
> 4.6.0 20101106 - 2124K c/s, 29848 bytes
> 4.6.0 20101204 - 2114K c/s, 29624 bytes
> 4.6.3 20111230 - 2116K c/s, 29624 bytes
> 4.7.0 20111231 - 2147K c/s, 29692 bytes
> 
> (This is for "Traditional DES", "many salts".)

The above was for gcc snapshots (not releases).  Here are some numbers
for gcc releases:

4.0.0 - 383K c/s, 71879 bytes (this old version of gcc generates function calls for SSE2 intrinsics)
4.1.0 - 2959K c/s, 28182 bytes
4.1.2 - 2964K c/s, 28365 bytes
4.2.0 - 2968K c/s, 28363 bytes
4.2.4 - 2971K c/s, 28382 bytes
4.3.0 - 2971K c/s, 28229 bytes
4.3.6 - 2959K c/s, 28229 bytes
4.4.0 - 2625K c/s, 29770 bytes
4.4.6 - 2695K c/s, 29316 bytes
4.5.0 - 2729K c/s, 29203 bytes
4.5.3 - 2716K c/s, 29203 bytes
4.6.0 - 2111K c/s, 29624 bytes
4.6.2 - 2123K c/s, 29624 bytes

(all of these are with DES_BS_ASM forcibly disabled)

So things were really good for versions 4.1.0 through 4.3.6, but started
to get worse afterwards and got really bad with 4.6.

To be fair, things are very different for some other hash/cipher types
supported by JtR - e.g., for Blowfish-based hashing we went from 560 c/s
for 4.1.0 to 700 c/s for 4.6.2.

Alexander

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.