summaryrefslogtreecommitdiff
path: root/lib
diff options
context:
space:
mode:
authorarezaii <Ahmad.rezaii@hpe.com>2024-09-26 21:39:14 -0600
committerGitHub <noreply@github.com>2024-09-27 05:39:14 +0200
commit1d06a324b5ba59f2b0d50248e8ad8a484ae7cbe7 (patch)
treebf2a173776c71752899682f613340d6b093975cc /lib
parent20f90dcda20afaf823fd1e73f4273d5cd5a46e4c (diff)
downloadspack-1d06a324b5ba59f2b0d50248e8ad8a484ae7cbe7.tar.gz
spack-1d06a324b5ba59f2b0d50248e8ad8a484ae7cbe7.tar.bz2
spack-1d06a324b5ba59f2b0d50248e8ad8a484ae7cbe7.tar.xz
spack-1d06a324b5ba59f2b0d50248e8ad8a484ae7cbe7.zip
Chapel 2.2 update (#46593)
* shorten version number validations per reviewer feedback * rename set_lib_path per reviewer feedback * Add E4S tag * Set CHPL_CUDA_PATH to ensure Chapel installer finds the right package * Update ROCm dependency for Chapel 2.2 * Fix llvm-amdgpu and CHPL_TARGET_* for llvm=bundled * Ensure CHPL_TARGET_COMPILER is set to "llvm" when required (llvm=spack or +cuda or +rocm). * Ensure CHPL_TARGET_{CC,CXX} are only set when using llvm=spack or llvm=none * Use hip.prefix to set CHPL_ROCM_PATH Since we might not directly depend on llvm-amdgpu, thus it might not appear in our spec * limit m4 dependency to +gmp * limit names of env vars created from variants * Ensure that +cuda and +rocm variants are Sticky The concretizer should never be permitted to select GPU support, because it's only meaningful and functional when the appropriate hardware is actually available, and the concretizer cannot reliably determine that. Also: Chapel's GPU support includes alot of complicated dependencies and constraints, so leaving that choice free to the concretizer leads to alot of extraneous and confusing messages when failing to concretize a non-GPU-enabled spec. Co-authored-by: Dan Bonachea <dobonachea@lbl.gov>
Diffstat (limited to 'lib')
0 files changed, 0 insertions, 0 deletions