From tk @end|ng |rom tkoen|g@net  Sat May  4 18:59:12 2019
From: tk @end|ng |rom tkoen|g@net (=?UTF-8?Q?Thomas_K=c3=b6nig?=)
Date: Sat, 4 May 2019 18:59:12 +0200
Subject: [Rd] R problems with lapack with gfortran
In-Reply-To: <20190504164903.GB15478@troutmask.apl.washington.edu>
References: <ff60d7f9-e54d-473a-bc85-7989abc887da@tkoenig.net>
 <b24b0ef5-1f45-1a03-4153-f335e4f1f8a5@gmail.com>
 <2e68f333-1d10-02d4-3560-4b1b9d773a52@tkoenig.net>
 <6E812A6F-91B2-4412-A536-2CD672C5F4BA@xs4all.nl>
 <D521C66E-D67E-4C17-98EF-D651026561ED@gmail.com>
 <79689a6a-077c-019a-d16a-597d7b60199d@tkoenig.net>
 <20190504164903.GB15478@troutmask.apl.washington.edu>
Message-ID: <1bd74386-737b-724a-f27b-73a790d1cea7@tkoenig.net>

Hi Steve,

> With the caveat that one may need to use the VALUE attribute to
> account for pass-by-value vs pass-by-reference.

LAPACK should be all pass by reference, it is old F77-style
code (except that the odd ALLOCATABLE array has snuck in
in the testing routines).



[Rd] R problems with lapack with gfortran
=?UTF-8?Q?Thomas_K=c3=b6nig?=