[llvm] r206211 - [ARM64][MC] Set the default CPU to cyclone when initilizating the MC layer.

[Jiangning Liu]

Hi,

Should the root cause of this issue be cross-target compilation? If one day
AArch64 is strong enough for native software ecosystem, I would be hoping
to simply use host as the target and it should be the most natural way we
should do.

Thanks,
-Jiangning


2014-04-17 3:58 GMT+08:00 Andrew Trick <atrick at apple.com>:

>
> On Apr 16, 2014, at 12:37 PM, Tim Northover <t.p.northover at gmail.com>
> wrote:
>
> >> Of course a target should be able to provide a cpu type called
> “generic" if
> >> it wants to. If the driver for some platform decides to use “generic”
> as the
> >> default, that’s fine with me. For ARM64, “generic" doesn’t seem very
> useful
> >> except to test certain features of the backend, and certainly should
> not be
> >> a default.
> >
> > That "except" is rather important to me. I'd really rather not have to
> > remember to specify a valid "-mcpu" every time I execute llc, if I
> > understand you correctly. I'm annoyed enough by the regular intrusion
> > of "-mattr=neon" and friends.
> >
> > I suppose if anything I'd want llc to choose a maximal sensible CPU
> > rather than a minimal one. Possibly with its own logic.
>
> You’re asking for logic to pick a platform-specific default to be in a
> library that can be used by both clang and llc. That sounds great to me, as
> long as clang/llc are consistent. It’s just more work than forcing llc to
> take explicit options and less important to me.
>
> -Andy
>
> > Cheers.
> >
> > Tim.
>
>
> _______________________________________________
> llvm-commits mailing list
> llvm-commits at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvm-commits
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-commits/attachments/20140417/64d3926e/attachment.html>