<html><head></head><body><div style="color:#000; background-color:#fff; font-family:HelveticaNeue, Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font-size:10px"><div id="yui_3_16_0_ym19_1_1466778302393_60252"><font size="3" id="yui_3_16_0_ym19_1_1466778302393_60352">Hi All,</font></div><div id="yui_3_16_0_ym19_1_1466778302393_60253"><font size="3"><br id="yui_3_16_0_ym19_1_1466778302393_60254"></font></div><div id="yui_3_16_0_ym19_1_1466778302393_60255"><font size="3">While using clang driver to create binary for aarch64 subtarget, </font></div><div id="yui_3_16_0_ym19_1_1466778302393_60256"><font size="3">do we need to give any other flag apart from '--target=aarch64-linux-gnu -mcpu=<> -mtune=<>' for using a AArch64's subtarget scheduling model?</font></div><div id="yui_3_16_0_ym19_1_1466778302393_60257"><font size="3">I see same executable (in size & contents) generated for subtargets of aarch64 such as cortex-a57, exynos-m1 & kryo even after replacing the cpu names. </font></div><div id="yui_3_16_0_ym19_1_1466778302393_60258"><font size="3">Should I include some other flag ?</font></div><div id="yui_3_16_0_ym19_1_1466778302393_60259"><font size="3"><br id="yui_3_16_0_ym19_1_1466778302393_60260"></font></div><div id="yui_3_16_0_ym19_1_1466778302393_60261"><font size="3">clang++ --target=aarch64-linux-gnu -mcpu=exynos-m1 -mtune=exynos-m1 way_mkbound.cpp -o my.out</font></div><div id="yui_3_16_0_ym19_1_1466778302393_60262"><font size="3"><br id="yui_3_16_0_ym19_1_1466778302393_60263"></font></div><div id="yui_3_16_0_ym19_1_1466778302393_60264"><font size="3">With Regards,</font></div><div dir="ltr" id="yui_3_16_0_ym19_1_1466778302393_60265"><font size="3" id="yui_3_16_0_ym19_1_1466778302393_60354">Pankaj</font></div></div></body></html>