{"push_id":2612693199,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"a005e7434fa933a809eea8af731be2e2b67dc35f","before":"d44047c0e643e6f332fee863a7504849e3868f80","commits":[{"sha":"a005e7434fa933a809eea8af731be2e2b67dc35f","author":{"name":"John McCall","email":"d279088d79e357a153f8842902bcfc9d630ff5da@apple.com"},"message":"Cap \"voluntary\" vector alignment at 16 for all Darwin platforms.\n\nThis fixes two major problems:\n- We were not capping vector alignment as desired on 32-bit ARM.\n- We were using different alignments based on the AVX settings on\n  Intel, so we did not have a consistent ABI.\n\nThis is an ABI break, but we think we can get away with it because\nvectors tend to be used mostly in inline code (which is why not having\na consistent ABI has not proven disastrous on Intel).\n\nIntel's AVX types are specified as having 32-byte / 64-byte alignment,\nso align them explicitly instead of relying on the base ABI rule.\nNote that this sort of attribute is stripped from template arguments\nin template substitution, so there's a possibility that code templated\nover vectors will produce inadequately-aligned objects.  The right\nlong-term solution for this is for alignment attributes to be\ninterpreted as true qualifiers and thus preserved in the canonical type.","distinct":true,"url":"https://api.github.com/repos/llvm-project/llvm-project-20170507/commits/a005e7434fa933a809eea8af731be2e2b67dc35f"}]}
{"actor":{"display_login":"chapuni"}}