1 Reply Latest reply on Apr 18, 2013 9:49 AM by chipf

    ACML 5.3.0 headers: cunmr3_ and zunmr3_

    vero

      Is there a reason why cunmr3_ and zunmr3_ functions are declared twice in acml.h? Both seem to have declarations as LAPACK routines and auxiliaries.

       

      > grep -n cunmr3_ /opt/acml5.3.0/gfortran64/include/acml.h

      2619:extern void cunmr3_(char *side, char *trans, int *m, int *n, int *k, int *l, complex *a, int *lda, complex *tau, complex *c, int *ldc, complex *work, int *info, int side_len, int trans_len);

      3575:extern void cunmr3_(char *side, char *trans, int *m, int *n, int *k, int *l, complex *a, int *lda, complex *tau, complex *c, int *ldc, complex *work, int *info, int side_len, int trans_len);

      > grep -n zunmr3_ /opt/acml5.3.0/gfortran64/include/acml.h

      3444:extern void zunmr3_(char *side, char *trans, int *m, int *n, int *k, int *l, doublecomplex *a, int *lda, doublecomplex *tau, doublecomplex *c, int *ldc, doublecomplex *work, int *info, int side_len, int trans_len);

      4023:extern void zunmr3_(char *side, char *trans, int *m, int *n, int *k, int *l, doublecomplex *a, int *lda, doublecomplex *tau, doublecomplex *c, int *ldc, doublecomplex *work, int *info, int side_len, int trans_len);

        • Re: ACML 5.3.0 headers: cunmr3_ and zunmr3_
          chipf

          Sorry for the delay in answering, I somehow missed this as new post. 

           

          It seems the answer is no, there is no good reason.  It looks like this is just an oversight.   It does show up in both sections, and should be removed from one of them.

           

          We are about to post a new release, and this is too late to be included.  For now you can just delete one of the definitions.