Skip to content

controlling-compiler-optimization-flags review #162

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
boegel merged 1 commit into from
May 31, 2023
Merged

controlling-compiler-optimization-flags review #162

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/controlling-compiler-optimization-flags.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ it will not run on a system with an older Intel Nehalem processor.
One possible workaround for heterogeneous HPC clusters is to build as many copies of the software stack as you have
processor generations in your cluster, and to configure your system so each compute node uses the right software stack
matching its processor architecture type.
Details for one way of doing this, using automounter/autofs are available at <https://easybuilders.github.io/easybuild/files/sciCORE-software-management_20150611.pdf>.
Details for one way of doing this, using automounter/autofs are available at <https://easybuild.io/files/sciCORE-software-management_20150611.pdf>.

Another solution is to configure EasyBuild to not optimize for the processor architecture of the build host via
`--optarch`, see below.
Expand Down