From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org)
by nuthatch.gentoo.org with esmtp (Exim 4.54)
id 1F5ruh-00077A-03
for garchives@archives.gentoo.org; Sun, 05 Feb 2006 21:59:19 +0000
Received: from robin.gentoo.org (localhost [127.0.0.1])
by robin.gentoo.org (8.13.5/8.13.5) with SMTP id k15LvihJ026971;
Sun, 5 Feb 2006 21:57:44 GMT
Received: from priv-edtnes56.telusplanet.net (outbound01.telus.net [199.185.220.220])
by robin.gentoo.org (8.13.5/8.13.5) with ESMTP id k15Lvggb014317
for <gentoo-science@lists.gentoo.org>; Sun, 5 Feb 2006 21:57:43 GMT
Received: from [192.168.2.100] (really [205.250.219.151])
by priv-edtnes56.telusplanet.net
(InterMail vM.6.01.05.04 201-2131-123-105-20051025) with ESMTP
id <20060205215801.OYTN8779.priv-edtnes56.telusplanet.net@[192.168.2.100]>;
Sun, 5 Feb 2006 14:58:01 -0700
Date: Sun, 5 Feb 2006 13:57:46 -0800 (PST)
From: Jason Nielsen <jdn@cs.sfu.ca>
X-X-Sender: jdn@localhost
To: Alan Jackson <ajackson@oplnk.net>
cc: gentoo-science@lists.gentoo.org
Subject: Re: [gentoo-science] Problems emerging blas-atlas
In-Reply-To: <20060205142344.4f1d694e.ajackson@oplnk.net>
Message-ID: <Pine.LNX.4.63.0602051351520.14278@localhost>
References: <20060205142344.4f1d694e.ajackson@oplnk.net>
Precedence: bulk
List-Post: <mailto:gentoo-science@lists.gentoo.org>
List-Help: <mailto:gentoo-science+help@gentoo.org>
List-Unsubscribe: <mailto:gentoo-science+unsubscribe@gentoo.org>
List-Subscribe: <mailto:gentoo-science+subscribe@gentoo.org>
List-Id: Gentoo Linux mail <gentoo-science.gentoo.org>
X-BeenThere: gentoo-science@gentoo.org
Reply-to: gentoo-science@lists.gentoo.org
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Archives-Salt: b7973667-36a2-434d-a867-1053aff40d9f
X-Archives-Hash: e258f6f48e06be95c5ba23cff77ecf7a
On Sun, 5 Feb 2006, Alan Jackson wrote:
> I'm having problems emerging blas-atlas-3.6.0-r1 on my AMD64 X2 system.
> The configure drops into an infinite loop :
>
> I am now going to ask for two C compilers, and their associated flags.
> The first such set (CC & CCFLAGS) are used in compiling the non-generated
> ATLAS code. This code is written in normal C, and responds well to high
> levels of optimization. Typically, this is set to your default compiler,
> and your highest levels of optimization.
>
> The second set of C compilers (MCC & MMFLAGS) is used to compile the generated
> ATLAS code. Generated codes are written at a very low-level (think of C used
> as a kind of portable assembler). On many platforms, high levels of
> optimization are detrimental, as the compiler tries to pipeline a perfectly
> pipelined code, and succeeds in reducing performance substantially (this
> occurs on DEC ALPHAs & Sun UltraSparcs, for instance). If the default does
> not work for you, try a midrange optimization such as -O. The generated code
> does not alias any output arguments, so aliasing optimizations should be OK.
>
> Enter ANSI C compiler(CC) [/usr/bin/gcc]: Enter C Flags (CCFLAGS) [-fomit-frame-pointer -O -mfpmath=387 -m64]: Compiling with = '/usr/bin/gcc -fomit-frame-pointer -O -mfpmath=387 -m64' doesn't seem to work for me.
> Enter 1 to try different CC/flags, 0 to continue anyway [1]:
>
> I've turned in a bugzilla ticket - but I thought someone here might have
> a suggestion for my platform. Is there a compiler flag I should set that
> would make it happy? Mine are pretty simple : CFLAGS="-O2 -march=athlon-xp"
> This is a brand new system, so all the ebuilds from the kernel up are completely
> current.
>
Version 3.6.0 doesn't support AMD64 chips. You need to install the 3.7.11
devel version, it is portage but masked. If you are looking for a high
performance Lapack/BLAS for AMD64 you can also try the ACML library
(http://developer.amd.com/acml.aspx).
Cheers,
Jason
--
gentoo-science@gentoo.org mailing list