On Wed, Sep 27, 2017 at 06:25:56PM +0100, Christophe Lyon wrote:
> ping?
OK, thanks.
Reviewed-by: James Greenhalgh
James
>
> On 20 September 2017 at 15:17, Christophe Lyon
> wrote:
> > Hi,
> >
> > On 11 September 2017 at 10:45, Andrew Pinski wrote:
> >> On Tue, Jul 18, 2017 at 5:50 AM, Chri
ping?
On 20 September 2017 at 15:17, Christophe Lyon
wrote:
> Hi,
>
> On 11 September 2017 at 10:45, Andrew Pinski wrote:
>> On Tue, Jul 18, 2017 at 5:50 AM, Christophe Lyon
>> wrote:
>>> Hello,
>>>
>>> I've received a complaint that GCC for AArch64 would generate
>>> vectorized code relying on
Hi,
On 11 September 2017 at 10:45, Andrew Pinski wrote:
> On Tue, Jul 18, 2017 at 5:50 AM, Christophe Lyon
> wrote:
>> Hello,
>>
>> I've received a complaint that GCC for AArch64 would generate
>> vectorized code relying on unaligned memory accesses even when using
>> -mstrict-align. This is a p
On Tue, Jul 18, 2017 at 5:50 AM, Christophe Lyon
wrote:
> Hello,
>
> I've received a complaint that GCC for AArch64 would generate
> vectorized code relying on unaligned memory accesses even when using
> -mstrict-align. This is a problem for code where such accesses lead to
> memory faults.
>
> A
ping^3 ?
https://gcc.gnu.org/ml/gcc-patches/2017-07/msg01063.html
On 31 August 2017 at 11:22, Christophe Lyon wrote:
> ping^2 ?
>
>
> On 21 August 2017 at 15:04, Christophe Lyon
> wrote:
>> ping ?
>> https://gcc.gnu.org/ml/gcc-patches/2017-07/msg01063.html
>>
>> Christophe
>>
>>
>> On 18 July
ping^2 ?
On 21 August 2017 at 15:04, Christophe Lyon wrote:
> ping ?
> https://gcc.gnu.org/ml/gcc-patches/2017-07/msg01063.html
>
> Christophe
>
>
> On 18 July 2017 at 14:50, Christophe Lyon wrote:
>> Hello,
>>
>> I've received a complaint that GCC for AArch64 would generate
>> vectorized code
ping ?
https://gcc.gnu.org/ml/gcc-patches/2017-07/msg01063.html
Christophe
On 18 July 2017 at 14:50, Christophe Lyon wrote:
> Hello,
>
> I've received a complaint that GCC for AArch64 would generate
> vectorized code relying on unaligned memory accesses even when using
> -mstrict-align. This is
Hello,
I've received a complaint that GCC for AArch64 would generate
vectorized code relying on unaligned memory accesses even when using
-mstrict-align. This is a problem for code where such accesses lead to
memory faults.
A previous patch (r24) introduced
aarch64_builtin_support_vector_misa