-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Out of bounds accesses in gemv leading to segmentation faults on AMD Epyc #4013
Comments
Could be related to #3740 (which I had ascribed to GCC's tree-vectorizer that is now active by default in recent gcc versions). Unfortunately at the time the problem only showed up on non-Linux systems, so the compiler pragma to disable it in the affected files is currently ifdef'd to Windows and OSX only. (Anyway that workaround was only put in after 0.3.21) |
@martin-frbg it indeed seems related to #3740. I've compiled OpenBLAS with |
Probably needs more tests, but from the "experiences" gathered so far it may be sufficient to disable this on a per-file basis, i.e. by removing the preprocessor conditionals around the |
@martin-frbg unfortunately, #4014 is not sufficient. It fixes the issue related to linear solving, but I'm now getting crashes for SVD decomposition with complex floats. Disabling |
Damn autoclose... I had already suspected the same pragma would be necessary in the equivalent kernels for complex and for double. Guess I'll need to do a full Arrayfire build for testing eventually, and/or find a big x86 server. |
Hello,
I've originally reported the issue to ArrayFire, but I believe that I can now reproduce it without ArrayFire and it's really an issue in OpenBLAS.
I've created a gist with a minimal working prototype: https://gist.github.com/twesterhout/855a4268c357b7d504072d2445e529fc
If we compile the code
and then run it under valgrind
Here's the output:
The system that I tested on:
The text was updated successfully, but these errors were encountered: