RE: [PATCH V2] aarch64: Use Q-reg loads/stores in movmem expansion

2020-08-05 Thread Sudakshina Das
Sent: 05 August 2020 14:52 > To: Andreas Schwab > Cc: Sudakshina Das ; gcc-patches@gcc.gnu.org > Subject: Re: [PATCH V2] aarch64: Use Q-reg loads/stores in movmem > expansion > > Andreas Schwab writes: > > This breaks bootstrap. > > I've pushed the below

Re: [PATCH V2] aarch64: Use Q-reg loads/stores in movmem expansion

2020-08-05 Thread Richard Sandiford
Andreas Schwab writes: > This breaks bootstrap. I've pushed the below to fix this after bootstrapping & regression testing on aarch64-linux-gnu. Richard >From 4af98a21e10547679a643eed85d51aa5d7d2510b Mon Sep 17 00:00:00 2001 From: Richard Sandiford Date: Wed, 5 Aug 2020 12:56:41 +0100 Subject:

Re: [PATCH V2] aarch64: Use Q-reg loads/stores in movmem expansion

2020-08-05 Thread Andreas Schwab
This breaks bootstrap. during RTL pass: final ../../gcc/timevar.c: In member function ‘void timer::push_internal(timer::timevar_def*)’: ../../gcc/timevar.c:373:1: internal compiler error: output_operand: invalid expression as operand 373 | } | ^ 0xbabdff output_operand_lossage(char const

RE: [PATCH V2] aarch64: Use Q-reg loads/stores in movmem expansion

2020-08-04 Thread Sudakshina Das
Hi Richard > -Original Message- > From: Richard Sandiford > Sent: 31 July 2020 16:14 > To: Sudakshina Das > Cc: gcc-patches@gcc.gnu.org; Kyrylo Tkachov > Subject: Re: [PATCH V2] aarch64: Use Q-reg loads/stores in movmem > expansion > > Sudakshina Das writes

Re: [PATCH V2] aarch64: Use Q-reg loads/stores in movmem expansion

2020-07-31 Thread Richard Sandiford
Sudakshina Das writes: > Hi > > This is my attempt at reviving the old patch > https://gcc.gnu.org/pipermail/gcc-patches/2019-January/514632.html > > I have followed on Kyrill's comment upstream on the link above and I am using > the recommended option iii that he mentioned. > "1) Adjust the cop

[PATCH V2] aarch64: Use Q-reg loads/stores in movmem expansion

2020-07-28 Thread Sudakshina Das
Hi This is my attempt at reviving the old patch https://gcc.gnu.org/pipermail/gcc-patches/2019-January/514632.html I have followed on Kyrill's comment upstream on the link above and I am using the recommended option iii that he mentioned. "1) Adjust the copy_limit to 256 bits after checking AA