[cfe-dev] using clang driver to generate executable for different subtargets

[Pankaj Gode via cfe-dev]

Hi All,
While using clang driver to create binary for aarch64 subtarget, do we need to give any other flag apart from '--target=aarch64-linux-gnu -mcpu=<> -mtune=<>' for using a AArch64's subtarget scheduling model?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. Should I include some other flag ?
clang++ --target=aarch64-linux-gnu -mcpu=exynos-m1 -mtune=exynos-m1 way_mkbound.cpp  -o my.out
With Regards,Pankaj
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20160625/4bf760d9/attachment.html>