Determine/document support for AMD compilers (non-PrgEnv case)

[Paul Hargrove]

With the recent resolution of issue #525, we now document support for AMD's LLVM-based compilers via PrgEnv-amd and PrgEnv-aocc on the HPE Cray EX (Shasta) platform. However, we currently disclaim support for these same compilers on other systems.

We have been testing AOCC ("AMD Optimizing C/C++ and Fortran Compilers") on our Dirac cluster once per week since mid-April 2022 (47 weeks). In that time there have been no compile or run failures which I would consider to be attributable to the compiler.

Also since mid-April, we have included dirac-aocc and dirac-aocc_old in the default GitLab CI pipeline used for PR testing.

Based on this history, I am comfortable with documenting AMD's compilers as supported in our 2023.3.0 release. Please respond if you have objections, or if there are concerns you'd like me to address.

The scope of work includes not just the updates to INSTALL.md, but also the configure-time logic for compiler version checks in utils/systen-checks.sh. Therefore, I feel that if this issue is to be addressed for the 2023.3.0 release, we must do so prior to the March 9 "feature freeze" (not the later "docs freeze").

[Paul Hargrove]

Proposed resolution appears in PR#474

[Paul Hargrove]

Support AMD "AOCC" compilers on Linux

This commit updates INSTALL.md and utils/system-checks.sh to document support for AMD's "AMD Optimizing C/C++ and Fortran Compilers" on Linux x86_64 with a floor version corresponding to what we currently test. Logic in utils/system-checks.sh issues our standard "has not been validated" or "is known to lack the support" message if a too-old compiler is detected, depending on just how old it is.

Resolves issue #586 Determine/document support for AMD compilers (non-PrgEnv case)

→ <<cset 63cda72b27eb>>