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
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.
This pull request updates the Intel LLVM Fortran flags to use
-march=x86-64-v3instead of-march=core-avx2for better compatibility and performance. The changes affect theCHANGELOG.mdandcompiler/flags/IntelLLVM_Fortran.cmakefiles.Intel LLVM Fortran Flags Update:
CHANGELOG.md: Added an entry to reflect the update of Intel LLVM Fortran flags to use-march=x86-64-v3instead of-march=core-avx2.compiler/flags/IntelLLVM_Fortran.cmake:COREAVX2_FLAGwithMARCH_FLAGand updated its value to-march=x86-64-v3for AMD, Hygon, and Intel processors.GEOS_Fortran_Vect_Flagsto use the newMARCH_FLAGinstead ofCOREAVX2_FLAG.GEOS_Fortran_Aggressive_Flagsto use the newMARCH_FLAGinstead ofCOREAVX2_FLAG.