- Infos im HLRS Wiki sind nicht rechtsverbindlich und ohne Gewähr -
- Information contained in the HLRS Wiki is not legally binding and HLRS is not responsible for any damages that might result from its use -

Compiler(Hawk): Difference between revisions

From HLRS Platforms
Jump to navigationJump to search
No edit summary
No edit summary
Line 11: Line 11:
<br>
<br>


Please note that compilers do not use optimization flags by default at the moment. Hence, please refer to https://www.advancedhpc.com/wp-content/uploads/2018/10/EPYC-Compiler-Options-Quick-Ref-Guide.pdf and set the respective flags on your own. With respect to PGI, we recommend to use
Please note that compilers do not use optimization flags by default at the moment. Hence, please refer to [https://www.advancedhpc.com/wp-content/uploads/2018/10/EPYC-Compiler-Options-Quick-Ref-Guide.pdf Compiler Options Quick Reference Guide] and set the respective flags on your own (with -mznver1 for Naples and -mznver2 for Rome nodes). With respect to PGI, we recommend to use
<pre>
<pre>
<compiler> -tp=zen -O3
<compiler> -tp=zen -O3
</pre>
</pre>

Revision as of 15:42, 11 October 2019

The following compilers are available at Hawk:

  • GNU
  • AMD
  • PGI
  • Intel


We highly recommend to try as much of them as possible and compare the performance of the generated code! If you code according to language standards, this is almost for free but can give you a significant speedup! There is no such thing as an "ideal" compiler! One suites better to application A, one suites better to application B (cf. Best Practice Guide AMD EPYC (Naples)).


Please note that compilers do not use optimization flags by default at the moment. Hence, please refer to Compiler Options Quick Reference Guide and set the respective flags on your own (with -mznver1 for Naples and -mznver2 for Rome nodes). With respect to PGI, we recommend to use

<compiler> -tp=zen -O3