From: "Jean-François Caron" <jfcaron@phas.ubc.ca>
To: Patrick Alken <patrick.alken@Colorado.EDU>
Cc: "gsl-discuss@sourceware.org" <gsl-discuss@sourceware.org>
Subject: Re: GSL v2.0 discussion
Date: Fri, 04 Apr 2014 17:41:00 -0000 [thread overview]
Message-ID: <30FB3FFE-22DD-4876-946F-55C3441C33B9@phas.ubc.ca> (raw)
In-Reply-To: <533EE585.40301@colorado.edu>
> 1. Should we try to add lapack/flame interfaces for the 2.0 release or wait until 3.0?
Unless an individual specifically volunteers for this job, we should not delay.
> 2. Is it better to select gsllinalg/lapack/flame at compile time or link time?
Selecting at compile time sounds more reasonable. If a user really needs to use both LA libs with GSL, they should be advanced enough to be able to install parallel versions of GSL.
> 4. What should we do about error handling in libflame? Just accept the abort() behavior?
File a bug report with libflame?
> 5. Is there a strong preference for doing wrappers for both lapack and flame? Should we only interface to lapack, due to the difficulties with flame (global state, abort() error handling)? Should we only interface to flame due to its more modern design?
If only one of the libs was an option, I would vote for LAPACK, since it’s much more commonly used & well-known.
Jean-François
next prev parent reply other threads:[~2014-04-04 17:41 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 [this message]
2014-04-04 20:31 ` Rhys Ulerich
2014-04-04 20:52 ` Patrick Alken
2014-04-04 21:07 ` Patrick Alken
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=30FB3FFE-22DD-4876-946F-55C3441C33B9@phas.ubc.ca \
--to=jfcaron@phas.ubc.ca \
--cc=gsl-discuss@sourceware.org \
--cc=patrick.alken@Colorado.EDU \
/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).