Refs #83. Clang 3.1 works fine on Sandy Bridge Mac OSX. Edit the document.
This commit is contained in:
parent
98d004c50b
commit
fda5e0da8a
12
README
12
README
|
@ -34,8 +34,10 @@ Please read GotoBLAS_01Readme.txt
|
||||||
Additional support CPU:
|
Additional support CPU:
|
||||||
x86_64:
|
x86_64:
|
||||||
Intel Xeon 56xx (Westmere) //Used GotoBLAS2 Nehalem codes.
|
Intel Xeon 56xx (Westmere) //Used GotoBLAS2 Nehalem codes.
|
||||||
|
Intel Sandy Bridge
|
||||||
MIPS64:
|
MIPS64:
|
||||||
ICT Loongson 3A //Level 3 BLAS subroutines are optimized.
|
ICT Loongson 3A
|
||||||
|
ICT Loongson 3B (Experimental)
|
||||||
|
|
||||||
4.Usages
|
4.Usages
|
||||||
Link with libopenblas.a or -lopenblas for shared library.
|
Link with libopenblas.a or -lopenblas for shared library.
|
||||||
|
@ -70,10 +72,10 @@ OpenBLAS users mailing list: http://list.rdcps.ac.cn/mailman/listinfo/openblas
|
||||||
8.ChangeLog
|
8.ChangeLog
|
||||||
Please see Changelog.txt to obtain the differences between GotoBLAS2 1.13 BSD version.
|
Please see Changelog.txt to obtain the differences between GotoBLAS2 1.13 BSD version.
|
||||||
|
|
||||||
9.Known Issues
|
9.Troubleshooting
|
||||||
* The number of CPUs/Cores should less than or equal to 8*sizeof(unsigned long). On 64 bits, the limit
|
* Please use Clang version 3.1 and above to compile the library on Sandy Bridge microarchitecture. The Clang 3.0 will generate the wrong AVX binary code.
|
||||||
is 64. On 32 bits, it is 32.
|
* The number of CPUs/Cores should less than or equal to 256.
|
||||||
* On Loongson 3A. make test would be failed because of pthread_create error. The error code is EAGAIN. However, it will be OK when you run the same testcase on shell. I don't think this is a bug in OpenBLAS.
|
* On Loongson 3A. make test would be failed because of pthread_create error. The error code is EAGAIN. However, it will be OK when you run the same testcase on shell.
|
||||||
|
|
||||||
10. Specification of Git Branches
|
10. Specification of Git Branches
|
||||||
We used the git branching model in this article (http://nvie.com/posts/a-successful-git-branching-model/).
|
We used the git branching model in this article (http://nvie.com/posts/a-successful-git-branching-model/).
|
||||||
|
|
Loading…
Reference in New Issue