all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] Attempt to fix OpenBLAS on MIPS.
Date: Tue, 21 Jul 2015 11:15:10 -0400	[thread overview]
Message-ID: <87zj2p1r0h.fsf@netris.org> (raw)
In-Reply-To: <idjmvyr2cty.fsf@bimsb-sys02.mdc-berlin.net> (Ricardo Wurmus's message of "Mon, 20 Jul 2015 15:11:37 +0200")

Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de> writes:

> Attached is a patch that *might* fix the build of OpenBLAS on MIPS.
>
> The LOONGSON3A and LOONGSON3B targets both enable the use of special
> extended instructions which may not be available on other MIPS CPUs.
> This patch forces the SICORTEX target to be used, which should limit the
> code to only standard MIPS instructions.
>
> I don’t know if this would actually work and I note that SICORTEX is
> listed as a “mips” target, rather than “mips64”, so maybe this is doomed
> to fail.  I would appreciate it if someone with a MIPS machine could
> test this patch.

With this patch, openblas builds successfully on mips64el, although I
cannot say whether it works, since there are no tests.

Is there a (preferably not huge) package that uses openblas and has a
test suite that I could try?

      Mark

  reply	other threads:[~2015-07-21 15:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-20 13:11 [PATCH] Attempt to fix OpenBLAS on MIPS Ricardo Wurmus
2015-07-21 15:15 ` Mark H Weaver [this message]
2015-07-21 16:48   ` Mark H Weaver
2015-07-22 15:59     ` Ricardo Wurmus
2015-07-22 17:19       ` Andreas Enge
2015-07-22 20:02         ` Mark H Weaver
2015-07-22 20:07           ` Mark H Weaver
2015-08-24 12:28             ` Ricardo Wurmus
2015-09-24  8:27               ` Ricardo Wurmus
2015-07-23  1:28           ` Mark H Weaver

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=87zj2p1r0h.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guix-devel@gnu.org \
    --cc=ricardo.wurmus@mdc-berlin.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.