From: Brian Gough <bjg@gnu.org>
To: Gerard Jungman <jungman@lanl.gov>
Cc: GSL Discuss Mailing List <gsl-discuss@sourceware.org>
Subject: Re: libflame version 4.0 announced
Date: Wed, 17 Feb 2010 21:20:00 -0000 [thread overview]
Message-ID: <87aav7r2u4.wl%bjg@network-theory.co.uk> (raw)
In-Reply-To: <1266363451.8015.153.camel@manticore.lanl.gov>
At Tue, 16 Feb 2010 16:37:31 -0700,
Gerard Jungman wrote:
> (2) The LAPACK-like coverage seems reasonable. But I am not a good
> judge of this. How much LAPACK functionality is covered in
> this latest release? Obviously all the banded-matrix stuff
> is out, since libflame does nothing with banded matrices.
> But how complete is it regarding core functionality?
The main omissions currently are eigenvalues and SVD.
However, since everything in FLAME is derived automatically from a
high-level description it should be easier for them to add new
algorithms in the long run.
The problems below are all fixable I am sure.
> (4) According to the manual, libflame calls abort() when it encounters
> a problem. As I have discussed before, this is brain-damaged. It
> makes it hard for other library developers (us) to integrate
> their thing into an existing error-handling system. They seem
> to admit it is a problem, but it's probably a low priority
> for them. How can we integrate this?
>
> (5) There are many configuration/build options. Is it feasible to
> build and deploy several different versions (with and without
> SuperMatrix, etc), from which a selection can be made at link
> time, requiring no source-level changes in client code?
> (d) There are several places where the API assumes C stdio. It looks
> like some of these uses are internal (like FLA_Print_message
> being used for error messages). This is brain-damaged, since
> it makes it harder to integrate into other environments
> (i.e. C++) where C stdio is not appropriate. It's ok to
> have such "convenience" functions in the API, but they
> should not be used internally.
>
> (e) The autotools build looks somewhat annoying. I'm really
> tired of autotools. Obviously, the same is true of GSL.
next prev parent reply other threads:[~2010-02-17 21:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 8:19 GSL extension ode-initval2-1.0 released Tuomo Keskitalo
2010-01-22 9:16 ` [Help-gsl] " Forest Yang
2010-01-23 11:15 ` Tuomo Keskitalo
2010-02-16 23:36 ` libflame version 4.0 announced Gerard Jungman
2010-02-17 21:20 ` Brian Gough [this message]
2010-02-17 22:49 ` Gerard Jungman
2010-02-17 23:10 ` Rhys Ulerich
2010-02-19 18:19 ` Brian Gough
2010-02-17 22:51 ` James Amundson
2010-02-14 6:15 Rhys Ulerich
2010-02-17 21:20 ` Brian Gough
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=87aav7r2u4.wl%bjg@network-theory.co.uk \
--to=bjg@gnu.org \
--cc=gsl-discuss@sourceware.org \
--cc=jungman@lanl.gov \
/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).