Re: [ARM][PR65768] Keep constants in register when expanding

2015-05-14 Thread Richard Earnshaw
On 27/04/15 00:07, Kugan wrote: While I support your goals, I think your approach needs some refinement. In particular, we DO NOT want another function that starts looking at constant values and tries to decide, on a case by case basis, what to do with that value. We need to keep the logic fo

Re: [ARM][PR65768] Keep constants in register when expanding

2015-05-13 Thread Kugan
Ping ? Thanks, Kugan On 27/04/15 09:07, Kugan wrote: > >> While I support your goals, I think your approach needs some refinement. >> >> In particular, we DO NOT want another function that starts looking at >> constant values and tries to decide, on a case by case basis, what to do >> with that

Re: [ARM][PR65768] Keep constants in register when expanding

2015-04-26 Thread Kugan
> While I support your goals, I think your approach needs some refinement. > > In particular, we DO NOT want another function that starts looking at > constant values and tries to decide, on a case by case basis, what to do > with that value. We need to keep the logic for that, as much as > poss

Re: [ARM][PR65768] Keep constants in register when expanding

2015-04-18 Thread Richard Earnshaw
On 15/04/15 08:48, Kugan wrote: > As mentioned in PR65768, ARM gcc generates suboptimal code for constant > Uses in loop. Part of the reason is that ARM back-end is splitting > constants during expansion of RTL, making it hard for the RTL > optimization passes to optimize it. Zhenqiang posted a pat

Re: [ARM][PR65768] Keep constants in register when expanding

2015-04-15 Thread Kugan
On 15/04/15 18:21, Kyrill Tkachov wrote: > Hi Kugan, > > On 15/04/15 08:48, Kugan wrote: >> As mentioned in PR65768, ARM gcc generates suboptimal code for constant >> Uses in loop. Part of the reason is that ARM back-end is splitting >> constants during expansion of RTL, making it hard for the R

Re: [ARM][PR65768] Keep constants in register when expanding

2015-04-15 Thread Kyrill Tkachov
Hi Kugan, On 15/04/15 08:48, Kugan wrote: As mentioned in PR65768, ARM gcc generates suboptimal code for constant Uses in loop. Part of the reason is that ARM back-end is splitting constants during expansion of RTL, making it hard for the RTL optimization passes to optimize it. Zhenqiang posted

[ARM][PR65768] Keep constants in register when expanding

2015-04-15 Thread Kugan
As mentioned in PR65768, ARM gcc generates suboptimal code for constant Uses in loop. Part of the reason is that ARM back-end is splitting constants during expansion of RTL, making it hard for the RTL optimization passes to optimize it. Zhenqiang posted a patch at https://gcc.gnu.org/ml/gcc-patches