Re: [PATCH][ARM] Improve cond_exec opportunities for immediate shifts for -mrestrict-it

2013-09-10 Thread Richard Earnshaw
On 10/09/13 14:11, Kyrylo Tkachov wrote: >> On 09/09/13 17:32, Kyrylo Tkachov wrote: >>> Hi all, >>> >>> Shift operations with an immediate can generate a 16-bit encoding when >>> the immediate is 5-bit wide, i.e. in the range [0-31]. Therefore we >>> can use them in IT blocks even with the -mrestr

RE: [PATCH][ARM] Improve cond_exec opportunities for immediate shifts for -mrestrict-it

2013-09-10 Thread Kyrill Tkachov
> On 09/09/13 17:32, Kyrylo Tkachov wrote: > > Hi all, > > > > Shift operations with an immediate can generate a 16-bit encoding when > > the immediate is 5-bit wide, i.e. in the range [0-31]. Therefore we > > can use them in IT blocks even with the -mrestrict-it rules. > > > > I decided to reuse t

Re: [PATCH][ARM] Improve cond_exec opportunities for immediate shifts for -mrestrict-it

2013-09-10 Thread Richard Earnshaw
On 09/09/13 17:32, Kyrylo Tkachov wrote: > Hi all, > > Shift operations with an immediate can generate a 16-bit encoding when the > immediate is 5-bit wide, i.e. in the range [0-31]. Therefore we can use them > in IT blocks even with the -mrestrict-it rules. > > I decided to reuse the "N" constra

[PATCH][ARM] Improve cond_exec opportunities for immediate shifts for -mrestrict-it

2013-09-09 Thread Kyrylo Tkachov
Hi all, Shift operations with an immediate can generate a 16-bit encoding when the immediate is 5-bit wide, i.e. in the range [0-31]. Therefore we can use them in IT blocks even with the -mrestrict-it rules. I decided to reuse the "N" constraint with a slight modification by removing the !TARGET_