Project

General

Profile

Task #2699

Test POWER9

Added by Mark Abraham about 2 years ago. Updated 11 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
core library
Difficulty:
uncategorized
Close

Description

Mark and Szilard have access at BSC.

xlc 16.1 still cannot compiler c++11 in its c++11 mode, so I propose we ban that compiler so people don't waste time trying


Subtasks

Feature #2748: Power9 build system supportClosed
Task #2772: check performance on POWER9Rejected

History

#1 Updated by Erik Lindahl almost 2 years ago

I would rather suggest to keep it simple and not add more CMake code for corner cases - we can test for specific features, or simply accept that some broken compilers will result in things crashing.

For cases where there are silent bugs we might need specific code to ban compilers, but otherwise I would suggest that we avoid adding a ton of code checking specific compiler versions that we then need to keep testing and modifying every release!

#2 Updated by Mark Abraham almost 2 years ago

Erik Lindahl wrote:

I would rather suggest to keep it simple and not add more CMake code for corner cases - we can test for specific features, or simply accept that some broken compilers will result in things crashing.

OK, but you're the one who wants to stop checking in our CMake for c++11 features that don't work :-) e.g. adding

class temp
{
  int x[2] = {0, 0};
};

in the existing checks for c++11 compatibility of the compiler is likely enough to effectively ban the xlc with which I've noticed a compilation error for that kind of construct. IMO that is what we should do.

For cases where there are silent bugs we might need specific code to ban compilers, but otherwise I would suggest that we avoid adding a ton of code checking specific compiler versions that we then need to keep testing and modifying every release!

Sure, I'd much rather have a feature test than a specific disabling

#3 Updated by Szilárd Páll almost 2 years ago

#4 Updated by Paul Bauer almost 2 years ago

  • Target version changed from 2019 to 2020

retargeted to 2020

#5 Updated by Paul Bauer 11 months ago

  • Target version changed from 2020 to 2021-infrastructure-stable

#6 Updated by Mark Abraham 11 months ago

If POWER9 is now a "best effort support" platform that we won't test this year, we should agree to not test it until some new development in POWER space

#7 Updated by Szilárd Páll 11 months ago

This issues seems to be more about xlc rather than Power, so the title seems is slightly misleading.

I've built and ran on Power9 just recently, so it is not exactly untested. We also do have hardware (that now works with a CUDA GPU too), so not harder to do basic sanity check than on most other platforms.
(As a side-note we have users at ORNL (and Livermore too I think) using GROMACS on Summit and Sierra and we've discussed engaging with them to get help with testing -- perhaps it is worth following up on that?)

#8 Updated by Szilárd Páll 11 months ago

2020 beta3 builds and passed tests on our Raptor Talos II Power9 with + an NVIDIA GPU using gcc 8.3 and 9.2 + CUDA 10.1.

#9 Updated by Mark Abraham 11 months ago

xlc is already not supported, so I agree that that earlier conversation is no longer relevant.

After Szilard's report, I guess we regard Power as tested for 2020

Also available in: Atom PDF