#10285: Adding support to an ARM processor
----------------------+-----------------------------------------------------
Reporter: Snark | Owner: GeorgSWeber
Type: defect | Status: new
Priority: major | Milestone:
Component: build | Keywords: ARM
Author: | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
----------------------+-----------------------------------------------------
Comment(by Snark):
Replying to [comment:12 vbraun]:
> Often, errors during ATLAS build are no problem: The tuning process
builds different assembly implementations to benchmark on your particular
hardware and its OK if these fail. Of course some errors, on the other
hand, are genuine bugs ;-) You could try #10226, although I doubt that it
would make any difference on ARM.
Those errors are not during the build when ATLAS tries to optimize. They
happen during the configuration, when ATLAS decides what it will try. This
step definitely doesn't work with that processor, and their organisation
is so special I haven't understood how it works yet. The only
documentation I found was how to use it when it works -- not how to extend
and fix it.
I reported the issue upstream as :
https://sourceforge.net/tracker/index.php?func=detail&aid=3111857&group_id=23725&atid=379483
I'm now fully stuck... :-(
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10285#comment:13>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
