Re: [PATCH] alpha: Use TARGET_COMPUTE_FRAME_LAYOUT

2019-06-05 Thread Uros Bizjak
> At the same time, merge several related frame computing functions. > Recall that HWI is now always 64-bit, so merge IMASK and FMASK, > which allows merging of several loops within prologue and epilogue. > > Full regression testing will take some time, but a quick browse > suggests no change in ge

Re: [PATCH] alpha: Use TARGET_COMPUTE_FRAME_LAYOUT

2018-07-10 Thread Richard Biener
On Tue, Jul 10, 2018 at 2:50 PM Richard Henderson wrote: > > On 07/10/2018 12:05 AM, Richard Biener wrote: > > On Mon, Jul 9, 2018 at 9:05 PM Richard Henderson wrote: > >> > >> At the same time, merge several related frame computing functions. > >> Recall that HWI is now always 64-bit, so merge I

Re: [PATCH] alpha: Use TARGET_COMPUTE_FRAME_LAYOUT

2018-07-10 Thread Richard Henderson
On 07/10/2018 12:05 AM, Richard Biener wrote: > On Mon, Jul 9, 2018 at 9:05 PM Richard Henderson wrote: >> >> At the same time, merge several related frame computing functions. >> Recall that HWI is now always 64-bit, so merge IMASK and FMASK, >> which allows merging of several loops within prolog

Re: [PATCH] alpha: Use TARGET_COMPUTE_FRAME_LAYOUT

2018-07-10 Thread Richard Biener
On Mon, Jul 9, 2018 at 9:05 PM Richard Henderson wrote: > > At the same time, merge several related frame computing functions. > Recall that HWI is now always 64-bit, so merge IMASK and FMASK, > which allows merging of several loops within prologue and epilogue. Btw, if you're not using these wit

[PATCH] alpha: Use TARGET_COMPUTE_FRAME_LAYOUT

2018-07-09 Thread Richard Henderson
At the same time, merge several related frame computing functions. Recall that HWI is now always 64-bit, so merge IMASK and FMASK, which allows merging of several loops within prologue and epilogue. Full regression testing will take some time, but a quick browse suggests no change in generated cod