From: "Tony Kelman" <tony@kelman.net>
To: <cygwin@cygwin.com>
Subject: Re: Tester for openblas needed
Date: Mon, 20 Oct 2014 16:16:00 -0000 [thread overview]
Message-ID: <BAY169-DS41999173A807A98C0210C7A7970@phx.gbl> (raw)
In-Reply-To: <54451D4C.5080604@gmail.com>
> look in the source package
> http://matzeri.altervista.org/x86_64/openblas/
Thanks. I'm a little surprised the cygblas-0.dll (x86_64, 0.2.12-1) does
not appear to be linked to libgfortran. Were you seeing your test
executables using multiple cores? I think you may have to build with
USE_THREAD=1 to enable threading (or USE_OPENMP=1 for openmp)?
I may be doing this wrong, but I'm getting errors from your openblas
build, but not the reference blas package, when I run the following:
$ curl -O
https://raw.githubusercontent.com/xianyi/OpenBLAS/develop/test/sblat2.f
$ gfortran -o sblat2 sblat2.f -lblas
$ rm -f SBLAT2.SUMM
$ curl
https://raw.githubusercontent.com/xianyi/OpenBLAS/develop/test/sblat2.dat |
./sblat2
This outputs messages like:
** On entry to SGEMV parameter number 1 had an illegal value
and so on for the other single-precision level 2 functions in that test.
This does seem to work okay on Linux or an existing i686-w64-mingw32 build.
-Tony
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2014-10-20 16:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 13:20 Marco Atzeri
2014-10-20 14:00 ` Tony Kelman
2014-10-20 14:34 ` Marco Atzeri
2014-10-20 16:16 ` Tony Kelman [this message]
2014-10-20 21:57 ` Marco Atzeri
2014-10-20 23:33 ` Tony Kelman
2014-10-21 5:48 ` Marco Atzeri
2014-10-21 11:56 ` Marco Atzeri
2014-10-21 12:39 ` Tony Kelman
2014-10-21 14:01 ` Marco Atzeri
2014-10-21 16:59 ` Achim Gratz
2014-10-21 17:49 ` Tony Kelman
2014-10-21 18:32 ` Marco Atzeri
2014-10-21 18:03 ` Marco Atzeri
2014-10-21 13:29 ` Marco Atzeri
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=BAY169-DS41999173A807A98C0210C7A7970@phx.gbl \
--to=tony@kelman.net \
--cc=cygwin@cygwin.com \
/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).