Skip to content
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

OpenBlas 0.3.13 fails to build with GNU 7.1.0 compilers (Stampede2) #258

Closed
naliboff opened this issue Aug 30, 2021 · 3 comments
Closed

Comments

@naliboff
Copy link

The default version of OpenBlas with the current version of Candi is 0.3.13. When building this version of OpenBlas on Stampede2 with GNU compilers (7.1.0), a series of errors is thrown of the following nature:
../kernel/x86_64/dasum_microk_skylakex-2.c:42:38: error: incompatible type for argument 1 of ‘_mm512_abs_pd’

This error is documented elsewhere (for example) and appears to be related to a bug in the GNU compilers.

Reverting to OpenBlas 0.3.7 produced no errors and allowed a successful build of trillions, deal.II 9.3.0, and ASPECT.

I'm not sure this is worth updating as the fix is documented on the ASPECT wiki and newer GNU compilers are now available on Stampede2, on which the issue may not exist.

@naliboff
Copy link
Author

For reference, the same error occurs with gcc 9.1.0

@tjhei
Copy link
Member

tjhei commented Aug 30, 2021

Are 7.1 and 9.1 the newest compilers installed on stampede2? Those are quite old.
I would agree that we don't do anything here and just point people to this issue to work around the issue.

@naliboff
Copy link
Author

Are 7.1 and 9.1 the newest compilers installed on stampede2?
These are the newest GCC compilers. There are much newer intel compilers, but I have still not been able to successfully build deal.II with the intel compilers on Stampede2 (I last tried 6-12 months ago). Should we revisit this? I recall one the Stampede2 folks was trying recently, as he posted on the ASPECT forums. Given you have compiled on Frontera, hopefully it is possible without a major effort.

I would agree that we don't do anything here and just point people to this issue to work around the issue.
👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants