help-octave
[Top][All Lists]
Advanced

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

Re: OfW + ATLAS


From: Paul Kienzle
Subject: Re: OfW + ATLAS
Date: Sat, 5 Oct 2002 20:40:35 -0500

I will repeat my suggestion here to use a DLL for LAPACK so that users
can drop in an ATLAS optimized for their architecture.  That will keep
the distribution size under control I hope.

Building the DLL is pretty painless.  You just need to have the following
line in your LAPACK makefile:

liblapack.dll: $(LAPACK_OBJ)
        gcc -shared -Wl, address@hidden -o $@ $^ -lsyslibs

where syslibs are whatever libs your lapack depends upon.  This creates
lapack.dll.a which you then link into octave using -llapack.dll.  Perhaps
the LAPACK/ATLAS build process for Windows already builds a DLL and
associated import library?

You will probably have to mod octave/acx_lapack.m4 to recognize
-llapack.dll.  Maybe you could get away with setting
--out-implib=liblapack.a and configuring octave with:

        LFLAGS=-Lpath/to/lapack ./configure ...

I'm assuming of course that linking is indeed dynamic under windows, and
that so long as the API remains unchanged the DLL's are interchangeable.
Is that the case?

Paul Kienzle
address@hidden

On Mon, Nov 04, 2002 at 07:57:17PM -0500, Andy Adler wrote:
> address@hidden wrote:
> 
> >A lot of people asked for an atlas optimized version of ofw. One of the 
> >first versions of ofw had the atlas package but although it worked fine 
> >(and fast) on any Intel x86 I had a lot of problems on AMD and Cyrix 
> >procs (hangs, unusual results, etc.) That's why I removed atlas.
> >
> >During the weekend I'll be making an atlas optimized version of ofw (as 
> >a separate version). I'll try to detect the cpu from the installer (I think 
> >I 
> >can) or I'll include a proper warning for the non-Intel users.
> >
> >  
> >
> 
> One issue with this is that each octave.exe is about 7-8 Meg, including 
> 3 or 4 of them with
> different ATLAS optimizations will make the install package big.
> 
> When I was doing the cygwin package on octave.sf.net, (with help from 
> Philip Nienhuis)
> I build ATLAS on a number of different machines (intel and AMD). I found
> that the pentiumIII ATLAS was the fastest for all architectures, even 
> compared
> to locally build ATLAS. The other advantage was that the pentiumIII 
> instruction
> set is (I thought) very well supported.
> 
> It surprises me that you have had AMD and Cyrix problems - could you 
> give some details.
> I think that ATLAS is such a win, that it would be a shame to be forced 
> to install
> a BLAS version anywhere.
> 
> --
> Andy Adler
> 
> 
> 
> -------------------------------------------------------------
> Octave is freely available under the terms of the GNU GPL.
> 
> Octave's home on the web:  http://www.octave.org
> How to fund new projects:  http://www.octave.org/funding.html
> Subscription information:  http://www.octave.org/archive.html
> -------------------------------------------------------------
> 



-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:  http://www.octave.org
How to fund new projects:  http://www.octave.org/funding.html
Subscription information:  http://www.octave.org/archive.html
-------------------------------------------------------------



reply via email to

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