octave-maintainers
[Top][All Lists]
Advanced

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

Re: Addition of ITSOL to MXE.


From: c.
Subject: Re: Addition of ITSOL to MXE.
Date: Sun, 30 Jun 2013 09:04:50 +0200

On 30 Jun 2013, at 08:50, marco atzeri <address@hidden> wrote:

> sure, and it can also trimmed down anyway as only
> "#ifdef _IBM" is different by "else"
> 
> these are not in realy needed
> #ifdef _SGI
> #ifdef _LINUX
> 
> I am also wondering why on _IBM
> the previous definition are not a problemm
> 
> #define qsplit qsplit_
> #define dgemv dgemv_
> #define readmtc readmtc_
> #define csrcsc csrcsc_
> #define coicsr coicsr_
> #define roscal roscal_
> #define coscal coscal_
> 
> but this change is needed
> 
> #ifdef _IBM
> #define dnrm2 dnrm2
> #define ddot ddot
> #define daxpy daxpy
> #else
> 
> as I know nothing on the IBM platform, I can not judge.
> Same for protos.h definitions


if F77_FUNC is used all this #idfef can go away, all is needed is

#include <config.h>
#define csrcsc F77_FUNC(csrcsc,CSRCSC)
…

autoconf will take care of the rest, no need to know the name of the platform.

>> And also something might need to be done to allow for combatibility with
>> Octave's new 64-bit indexing.
> 
> I am not familiar with it. I had the impression they need special built 
> blas/lapack libraries with also 64-bit indexing.
> 
> 
>> As the changes are getting a bit intrusive I think the upstream maintainers
>> should get involved from this early stage already.
> 
> A repository driven/coordinated by them will be needed, as I assume they
> already have further development underway.
> A dedicated mailing list will be also helpful


I'm afraid you're asking for too much here …

> Ruipeng,
> your opinion and preference ?
> 
c.



reply via email to

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