From: Andreas Enge <andreas@enge.fr>
To: Federico Beffa <beffa@ieee.org>
Cc: 18933@debbugs.gnu.org
Subject: bug#18933: ATLAS fails to build on mips
Date: Mon, 3 Nov 2014 22:27:45 +0100 [thread overview]
Message-ID: <20141103212745.GA29422@debian> (raw)
In-Reply-To: <CAKrPhPMqV9mJTTzvWG6xujnebjEAMUHddFgGWcq5Grg4X8PYKw@mail.gmail.com>
On Mon, Nov 03, 2014 at 06:53:35PM +0100, Federico Beffa wrote:
> * Are we corss-compiling, or are we on proper hardware?
No, it is native on a mips machine.
> I have no practical experience with MIPS, so my next question is: In
> the list of architectures supported by ATLAS I see:
> 49 = 'MIPSR1xK'
> 50 = 'MIPSICE9'
No idea. But there is a debian package for mipsel, described as
"The libraries in this package are built without any processor extension instructions, and should run on all processors of this general architecture, albeit less than optimally."
> Also ATLAS wants to know about ISA extensions. Is any of the following
> relevant or should I pick 'none'?
> none: 1
> VSX: 2
> AltiVec: 4
> AVXMAC: 8
> AVXFMA4: 16
> AVX: 32
> SSE3: 64
> SSE2: 128
> SSE1: 256
> 3DNow: 512
> NEON: 1024
2 and 4 are for powerpc, 8 to 512 for x86 and 1024 for arm. So "none"
should be best.
Andreas
next prev parent reply other threads:[~2014-11-03 21:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 9:33 bug#18933: ATLAS fails to build on mips Andreas Enge
2014-11-03 17:53 ` Federico Beffa
2014-11-03 21:27 ` Andreas Enge [this message]
2014-11-08 21:45 ` Federico Beffa
2014-11-09 9:29 ` Andreas Enge
2014-12-08 9:13 ` 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=20141103212745.GA29422@debian \
--to=andreas@enge.fr \
--cc=18933@debbugs.gnu.org \
--cc=beffa@ieee.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).