From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Tester for openblas needed
Date: Tue, 21 Oct 2014 05:48:00 -0000 [thread overview]
Message-ID: <5445F384.705@gmail.com> (raw)
In-Reply-To: <BAY169-DS201BCE4DCECE478E49F36BA7970@phx.gbl>
On 10/21/2014 1:33 AM, Tony Kelman wrote:
>> openblas is written in C
>
> More assembly than C according to github's count. I'm used to building
> the full version of openblas including their optimized implementations
> of lapack routines, which bring in libgfortran. So nevermind.
I avoided to include lapack as for compatibility
I will need to split exactly as netlib in
cygblas-0.dll
cyglapack-0.dll
something for the future.
>> USE_THREAD=1 and USE_OPENMP=1, can be used dynamically ;
>> if I am not wrong.
>
> What does your Makefile.conf say for NUM_CORES? I can't seem to get a
> test program with your build to use more than 2 cores (I have 4 + HT)
> by setting the OPENBLAS_NUM_THREADS environment variable.
NUM_CORES=2
I will ask on the OpenBlas mailing list
> -Tony
Regards
Marco
--
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-21 5:48 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
2014-10-20 21:57 ` Marco Atzeri
2014-10-20 23:33 ` Tony Kelman
2014-10-21 5:48 ` Marco Atzeri [this message]
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=5445F384.705@gmail.com \
--to=marco.atzeri@gmail.com \
--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).