-
Notifications
You must be signed in to change notification settings - Fork 370
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test segment fault on Intel Knight Landing #116
Comments
This is fixed by #117, which I will merge as soon as the tests pass. Note that you can also use icc for KNL (and other Intel archs) with |
Hi Devin, thank you for your work. But unfortunately you commit 7d42fc0 did not fix this bug. CI failed for KNL, too. |
The KNL CI failure is a red herring, it fails always for other technical reasons at the moment (not the least of which is that Travis doesn't have KNL nodes). I was able to compile and run the testsuite successfully using your configure line with gcc 6.2 and CentOS 7.2 on a Xeon Phi 7210. Could you please send a gdb backtrace of the failure as well as a disassembly of the region where it fails? |
Sure. I am installing gcc-6.3 to give it another shot.
|
@devinamatthews I am not suggesting that it is a practical solution, but you can make Travis CI execute code for a wide range of Intel processors using SDE. The public version of SDE supports most if not all of the publicly documented Intel instructions (Intel ISA extensions):
I will enqueue a low priority task to see if I can install and run SDE from within Travis. |
Yes, maybe this would be possible, but I imagine we would run into problems with the build time limit. |
Yeah, my understanding is that SDE emulation overhead is proportional to the percentage of instructions that need to be emulated and thus something like BLIS is going to run quite a bit slower when emulating AVX-512. I don't really know how Travis works on the back-end, but perhaps some day we will be able to request AWS C5 instances to get AVX-512 support, which would be the best available approximation to KNL. |
Thanks Devin! it has all the tests passed, and R is built against BLIS successfully. |
Thanks for working on this, Devin. |
Sure, Field. I don't think MKL suites my scientific needs to share results with colleagues and the public. I was introduced by Jeff from the OpenBLAS discussion. BLIS provided the only viable option on KNL, whose ecosystem is at present dominated by blackbox toolchains. Thanks again. Keep on this great work. I will give flame a try the other day for it is able to use the advanced API of BLIS compared to the reference lapack I am using. |
@heroxbd I assume your concern with MKL is that, because it is closed-source, it isn't fully reproducible and/or verifiable? I'm not in any way trying to talk you out of your principles, which I admire - I merely want to make sure I understand the concern precisely. BLIS is - as far as I know - the only open-source BLAS implementation that supports AVX-512 and I'm very happy that you are using it. While the proprietary Intel toolchain meets the needs of many users, it is important both to me and to others at Intel that there are high-quality open-source alternatives across the board. |
I configured blis by
and run tests by
make test
.On Intel broadwell it works, but fails by segment fault on Intel Knight Landing:
The log file is attached. My system is Gentoo with gcc-5.4.
build.log.gz
The text was updated successfully, but these errors were encountered: