See http://www.cryptopp.com/wiki/Build_Status_for_Crypto_5.6.1 for a list of
compilers/OS/CPU combinations that have been tested. Below are the major
changes from 5.6.0:
5.6.1 - added support for AES-NI and CLMUL instruction sets in AES and
GMAC/GCM
- removed WAKE-CFB
- fixed several bugs in the SHA-256 x86/x64 assembly code:
* incorrect hash on non-SSE2 x86 machines on non-aligned input
* incorrect hash on x86 machines when input crosses 0x80000000
* incorrect hash on x64 when compiled with GCC with optimizations
enabled
- fixed bugs in AES x86 and x64 assembly causing crashes in some MSVC
build configurations
- switched to a public domain implementation of MARS
- ported to MSVC 2010, Sun Studio 12u1
- renamed the MSVC DLL project to "cryptopp" for compatibility with
MSVC 2010
BTW, if anyone doesn't have a SVN client, you can get a tarball of the
current code from
http://cryptopp.svn.sourceforge.net/viewvc/cryptopp/trunk/c5/?view=tar
--------------------------------------------------
From: "Walter Villalba" <wvil...@gmail.com>
Sent: Wednesday, August 04, 2010 5:12 PM
To: "Crypto++ Users" <cryptop...@googlegroups.com>
Subject: Re: Crypto++ 5.6.1 release candidate
> When do you expect to have the final release ? Thanks.
>
> On Aug 4, 4:47 pm, "Wei Dai" <wei...@weidai.com> wrote:
>> Please grab r515 (the current trunk) from SVN and try it out. This
>> command:
>> "svn cohttps://cryptopp.svn.sourceforge.net/svnroot/cryptopp/trunk/c5c5"
>> will get it into a subdirectory called c5.
>>
>> See http://www.cryptopp.com/wiki/Build_Status_for_Crypto_5.6.1 for a list
>> of
>> compilers/OS/CPU combinations that have been tested. Below are the major
>> changes from 5.6.0:
>>
>> 5.6.1 - added support for AES-NI and CLMUL instruction sets in AES and
>> GMAC/GCM
>> - removed WAKE-CFB
>> - fixed several bugs in the SHA-256 x86/x64 assembly code:
>> * incorrect hash on non-SSE2 x86 machines on non-aligned input
>> * incorrect hash on x86 machines when input crosses 0x80000000
>> * incorrect hash on x64 when compiled with GCC with
>> optimizations
>> enabled
>> - fixed bugs in AES x86 and x64 assembly causing crashes in some
>> MSVC
>> build configurations
>> - switched to a public domain implementation of MARS
>> - ported to MSVC 2010, Sun Studio 12u1
>> - renamed the MSVC DLL project to "cryptopp" for compatibility with
>> MSVC 2010
>
> --
> You received this message because you are subscribed to the "Crypto++
> Users" Google Group.
> To unsubscribe, send an email to
> cryptopp-user...@googlegroups.com.
> More information about Crypto++ and this group is available at
> http://www.cryptopp.com.
>
I am some problems with compiling 5.6.1 prerelease for the Debian package:
In file included from camellia.cpp:16:
cpu.h:24: error: expected initializer before �_mm_shuffle_epi8�
cpu.h:34: error: �_mm_extract_epi32� declared as an �inline� variable
cpu.h:34: warning: �__gnu_inline__� attribute ignored
cpu.h:34: warning: �__always_inline__� attribute ignored
cpu.h:34: warning: �__artificial__� attribute ignored
cpu.h:34: error: �__m128i� was not declared in this scope
cpu.h:34: error: expected primary-expression before �const�
cpu.h:34: error: initializer expression list treated as compound expression
cpu.h:35: error: expected �,� or �;� before �{� token
cpu.h:41: error: expected initializer before �_mm_insert_epi32�
cpu.h:51: error: expected initializer before �_mm_clmulepi64_si128�
cpu.h:57: error: expected initializer before �_mm_aeskeygenassist_si128�
cpu.h:64: error: expected initializer before �_mm_aesimc_si128�
cpu.h:71: error: expected initializer before �_mm_aesenc_si128�
cpu.h:77: error: expected initializer before �_mm_aesenclast_si128�
cpu.h:83: error: expected initializer before �_mm_aesdec_si128�
cpu.h:89: error: expected initializer before �_mm_aesdeclast_si128�
I am compiling on architecture "i386" (specifically an old Pentium M
processor which is in my ThinkPad T42 laptop) using GCC 4.4.4.
emmintrin.h is included from cpu.h.
I know close to nothing about SSE stuff, but maybe you can guide me
through which test I should make?
Cheers,
/JP
It was a bug, where I had #if
defined(CRYPTOPP_BOOL_SSE2_INTRINSICS_AVAILABLE) in config.h, where it
should have been #if CRYPTOPP_BOOL_SSE2_INTRINSICS_AVAILABLE.
--------------------------------------------------
From: "Jens Peter Secher" <jpse...@gmail.com>
Sent: Sunday, August 08, 2010 1:03 PM
To: "Crypto++ Users" <cryptop...@googlegroups.com>
Subject: Re: Crypto++ 5.6.1 release candidate
> Hi,