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

[Renato Golin via cfe-dev]

On 25 June 2016 at 10:50, Pankaj Gode via cfe-dev
<cfe-dev at lists.llvm.org> wrote:
> 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?

Nope, that should be enough.


> 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 ?

Both M1 and Kryo have different scheduling parameters, but not
radically so. It's possible that your code is not hitting any of those
differences.

Perhaps if you could provide an example of what the code is and how
you expected it to be in the assembly output (maybe comparing with
GCC's output), we'd know what is not being done.

cheers,
-renato