[PATCH] D46042: Cap vector alignment at 16 for all Darwin platforms

[Steve Canon via Phabricator via cfe-commits]

scanon added a comment.

In https://reviews.llvm.org/D46042#1088044, @ab wrote:

> So, this makes sense to me, but on x86, should we also be worried about the fact that the calling convention is based on which features are available?  (>128bit ext_vector_types are passed in AVX/AVX-512 registers, if available).  Presumably swift is also affected, no?


Swift's calling conventions (will?) always divide larger vectors into 128b pieces. When interacting with C conventions, yes, this is still an issue.


Repository:
  rC Clang

https://reviews.llvm.org/D46042