From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] Add Julia.
Date: Thu, 26 Mar 2015 17:58:26 +0100 [thread overview]
Message-ID: <87d23vae6l.fsf@gnu.org> (raw)
In-Reply-To: <87twx7okgn.fsf@netris.org> (Mark H. Weaver's message of "Thu, 26 Mar 2015 11:19:04 -0400")
Mark H Weaver <mhw@netris.org> skribis:
> Mark H Weaver <mhw@netris.org> writes:
>
>> Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:
>>
>>> May I suggest adding passing the "DYNAMIC_ARCH=1" flag in openblas
>>> instead of propagating non-substitutability to Julia? When built with
>>> "DYNAMIC_ARCH=1" the CPU type can be picked with the environment
>>> variable OPENBLAS_CORETYPE=<type>. If I'm not mistaken this makes
>>> substitutions for openblas possible.
>>>
>>> What do you think?
>>
>> Yes, we should do this.
>
> When reading this the first time, somehow I managed to miss the fact
> that users will have to set OPENBLAS_CORETYPE to their CPU type.
Me too actually.
> Does that mean that openblas is unable to detect the CPU type
> automatically? What does it do if OPENBLAS_CORETYPE is unset?
>
> Will we have to set it during the build of packages that use openblas,
> such as Julia?
Good points, this is a bit scary. I assumed openblas would just detect
the CPU automatically at run time.
Ludo’.
next prev parent reply other threads:[~2015-03-26 16:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 11:16 [PATCH] Add Julia Ricardo Wurmus
2015-03-23 9:29 ` Ludovic Courtès
2015-03-23 21:35 ` Mark H Weaver
2015-03-24 14:56 ` Mark H Weaver
2015-03-24 17:14 ` Ricardo Wurmus
2015-03-24 20:45 ` Ludovic Courtès
2015-03-25 16:20 ` Mark H Weaver
2015-03-25 18:24 ` Ricardo Wurmus
2015-03-25 21:00 ` Mark H Weaver
2015-03-26 15:19 ` Mark H Weaver
2015-03-26 16:58 ` Ludovic Courtès [this message]
2015-03-26 21:14 ` Ricardo Wurmus
2015-03-29 13:21 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d23vae6l.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).