amd64 assembly for W64
lrn1986 at gmail.com
Sun Jan 9 00:57:25 CET 2011
On 08.01.2011 18:29, LRN wrote:
> On 03.01.2011 14:21, Werner Koch wrote:
>> On Fri, 31 Dec 2010 05:39, lrn1986 at gmail.com said:
>>> When configured with --disable-asm, libgcrypt successfully compiles
>>> and passes all the tests.
>> Then please do this. The asm support is pretty old and modern compilers
>> do a better job than most handcraftet asm.
>> Please use libgcrypt on W64 only for testing. We don't yet support it.
>> However, support is planned and Windows7 hardware arrived last week.
> Well, it's appears that i was a bit hasty in saying that everything
> works with --disable-asm.
> It works indeed - but only when compiled with -g -O0 (which i did for
> debugging purposes). Without CFLAGS="-g -O0" the resulting library
> still crashes during tests.
> I've studied it and discovered that it doesn't crash with -O1, but
> does with -O2 (which is the default when no -Ox option is specified).
> Then i've looked up in gcc documentation what -O1 and -O2 mean and
> started to test libgcrypt with different flags instead of -Ox.
> With CFLAGS="-O2 -fno-gcse" it produces a library that passes all
> My guess is that there's a bug in the version of gcc i'm using (4.6.0
> trunk), and a certain combination of optimizations simply makes it
> I'll try a different version of gcc (4.5.x, i think), but i'd have to
> build it first, which will take another day or so.
Yep, works with 4.5.2 (with just --disable-asm and the default -O2)
/me slaps himself for using an alpha version compiler
More information about the Gcrypt-devel