From: Patrick Alken <patrick.alken@Colorado.EDU>
To: gsl-discuss@sourceware.org
Subject: Re: GSL v2.0 discussion
Date: Fri, 04 Apr 2014 21:07:00 -0000 [thread overview]
Message-ID: <533F1EFB.6060007@colorado.edu> (raw)
In-Reply-To: <533F1BA7.5020003@colorado.edu>
On 04/04/2014 02:52 PM, Patrick Alken wrote:
> I need to look into whether lapack2flame accepts LAPACKE calls or just
> LAPACK calls (I don't see any reference to LAPACKE in the flame user
> manual). In any case, lapack is usually installed by default on many
> systems, whereas lapacke is probably not, so it may be worth supporting
> lapack instead.
Looking into this further it seems LAPACKE is included by default in
recent lapack installations, which is very nice. I like how LAPACKE
supports both row/column major matrix inputs - it seems this would make
things much easier for us and we still might be able to use lapack2flame
by linking with -llapacke but not -llapack?
next prev parent reply other threads:[~2014-04-04 21:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <533EE354.4050204@colorado.edu>
2014-04-04 17:02 ` Patrick Alken
2014-04-04 17:41 ` Jean-François Caron
2014-04-04 20:31 ` Rhys Ulerich
2014-04-04 20:52 ` Patrick Alken
2014-04-04 21:07 ` Patrick Alken [this message]
2014-04-14 14:08 ` Rhys Ulerich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=533F1EFB.6060007@colorado.edu \
--to=patrick.alken@colorado.edu \
--cc=gsl-discuss@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).