"Revert" Intel deprecation flag changes in spack's lib/spack/env/cc and pull in improved solution from spack mainline #1238
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR resolves #1230. Detailed information on what this PR does and why it is necessary is given in the issue. The improved solution does away with having to specify the
diag-disable
flags, since these are now set implicitly (and only during spack environment builds, not in downstream applications). Credits to Peter Scheibel from the spack core team for suggesting it and adding the spack unit tests to my implementation.Testing
oneapi
usingicx
,icpx
,ifort
and withintel
usingicc
,icpc
,ifort
)[email protected]
usingicx
,icpx
,ifort
)Applications affected
None
Systems affected
All using recent Intel compilers
Dependencies
Issue(s) addressed
Resolves #1230
Checklist