At Sun, 28 Jun 2009 17:26:39 +0200, José Luis García Pallero wrote: > Working with cblas_dgemv() function I can see various diferences between > refblas and gsl cblas implementations about invalid parameters. While in gsl > cblas the function only abort the execution because incorrect values in > "order" and "Trans" input parameters, in the refblas implementation the > function calls xerbla when M<0, N<0, LDA<max(1,M), incX==0 or incY==0 (in > this cases gsl cblas do not make operations and return). In the gsl_blas_* > wrapper this cases are not catched. This produces different executions if > you link your programs with gslcblas or refblas, lapack, atlas, etc. Are > these differences a known fact?
Good point, I *think* I considered this issue at the time but I don't remember and may have overlooked these. I will have to dig out the original BLAS paper and check whether the use of XERBLA was optional or part of the specification. -- Brian Gough (GSL Maintainer) Support freedom by joining the FSF http://www.fsf.org/associate/support_freedom/join_fsf?referrer=37 _______________________________________________ Help-gsl mailing list [email protected] http://lists.gnu.org/mailman/listinfo/help-gsl
