Intel classic compiler - #305
Merged
bcumming merged 3 commits intoAug 6, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add support for providing the "intel classic" compiler.
This is for supporting users who still have not migrated from the
ifortcompiler.It installs both
intel-oneapi-compilers(for C and C++) and theintel-oneapi-compilers-classic(for Fortran) Spack packages.The user probably has to hack the
preferline in theenvironments.yamldescription of the target environment.... but this is a rarely used feature that does not justify the refactoring required to make an elegant solution.