[PATCH] D110259: [SVE][Analysis] Tune the cost model according to the tune-cpu attribute

[Dave Green via Phabricator via llvm-commits]

dmgreen added a comment.

Would this be used as the expected vector width the vectorizer optimizes around? If so 4 for generic sounds a bit high and it should maybe be closer to the average of the hardware we expect to be out in the field. Likely 2 I would suspect.



================
Comment at: llvm/lib/Target/AArch64/AArch64Subtarget.cpp:371-373
+  if (TuneCPU == "generic") return 4;
+  else if (TuneCPU == "neoverse-v1") return 2;
+  else if (TuneCPU == "neoverse-n2") return 1;
----------------
These per-cpu values should probably be subtarget features or defined in AArch64Subtarget::initializeProperties like the other alignments and whatnot.


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D110259/new/

https://reviews.llvm.org/D110259