I have noticed that when doing a GCC/GCCcore build, it always uses the HOST architecture for -march and -mtune starting in compile stage 2, even though I have set something else via optarch. This is a real problem for heterogenous clusters if you do not make sure that the build host always is one with the oldest architecture, because then it leads to the error:

"internal compiler error: Illegal instruction"

when the resulting GCC is used on an older node.

Is this a known issue, or is there a way to make the GCC build process respect what EasyBuild sets as the target architecture, even during the later compile stages?

Thank you kindly in advance.

--
Maik Schmidt

Technische Universität Dresden
Zentrum für Informationsdienste und Hochleistungsrechnen (ZIH)
Willers-Bau A116
D-01062 Dresden
Telefon: +49 351 463-32836


Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to