[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnubg] gnubg on amd64 architecture

From: Christian Anthon
Subject: Re: [Bug-gnubg] gnubg on amd64 architecture
Date: Tue, 13 Feb 2007 20:26:26 +0100

On 2/13/07, Jim Segrave <address@hidden> wrote:

I just got a new laptop with an Intel Core2 Duo and tried building
gnubg there (gentoo Linux as FreeBSD can't currently support the
Radeon graphics chip nor the Intel sound chip :-(( )

I have a fix for the sse tests in neuralnet.c, which otherwise don't
compile (pushfl is not valid on this architecture, pushf pushes a 64
bit value, so the pop's must become popq's to 64 bit
registers). What's the best way of setting a #define so that
neuralnet.c can choose which assembler code to generate for 32 bit and
64 bit machines? #define ATHLON perhaps?

As a side note, when it wouldn't compile and before I found the AMD
instruction set documents, I tried building it with the -march=sse2
and -DUSE_SSE_VECTORIZE flags omitted (on a fresh fetch from cvs), yet
conf.h still had #define USE_SSE_VECTORISE 1, so the compile still
failed. What's the correct way of suppressing the sse code?

./configure --help | grep SSE

 --enable-sse=TYPE  enable SSE for newer cpus(TYPE=yes,no,cputest)

and with --enable-sse=yes sse is enabled and not tested for and I
think it is safe to assume the 64bit machines derived from the i386
architecture all have sse enabled cpus. The current default is

In case you really want to make cpu dependent options configure does
some host checks which on my amd64 result in host=x86_64.

Everything in config.h is controlled through configure, either by
config-checks or by command line options. If you really need to, you
may edit config.h by hand after running configure.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]