Re: [PATCH] disable aggressive_loop_optimizations until niter ready

2022-01-18 Thread Richard Biener via Gcc-patches
On Tue, 18 Jan 2022, Richard Biener wrote: > On Mon, 17 Jan 2022, Jiufu Guo wrote: > > > Richard Biener writes: > > > > > On Fri, 14 Jan 2022, Jiufu Guo wrote: > > > > > >> Richard Biener writes: > > >> > > >> > On Thu, 13 Jan 2022, guojiufu wrote: > > >> > > > >> >> On 2022-01-03 22:30, Rich

Re: [PATCH] disable aggressive_loop_optimizations until niter ready

2022-01-18 Thread Richard Biener via Gcc-patches
On Mon, 17 Jan 2022, Jiufu Guo wrote: > Richard Biener writes: > > > On Fri, 14 Jan 2022, Jiufu Guo wrote: > > > >> Richard Biener writes: > >> > >> > On Thu, 13 Jan 2022, guojiufu wrote: > >> > > >> >> On 2022-01-03 22:30, Richard Biener wrote: > >> >> > On Wed, 22 Dec 2021, Jiufu Guo wrote:

Re: [PATCH] disable aggressive_loop_optimizations until niter ready

2022-01-17 Thread Jiufu Guo via Gcc-patches
Richard Biener writes: > On Fri, 14 Jan 2022, Jiufu Guo wrote: > >> Richard Biener writes: >> >> > On Thu, 13 Jan 2022, guojiufu wrote: >> > >> >> On 2022-01-03 22:30, Richard Biener wrote: >> >> > On Wed, 22 Dec 2021, Jiufu Guo wrote: >> >> > >> >> >> Hi, >> >> >> ... >> >> >> >> >> >> Boots

Re: [PATCH] disable aggressive_loop_optimizations until niter ready

2022-01-14 Thread Richard Biener via Gcc-patches
On Fri, 14 Jan 2022, Jiufu Guo wrote: > Richard Biener writes: > > > On Thu, 13 Jan 2022, guojiufu wrote: > > > >> On 2022-01-03 22:30, Richard Biener wrote: > >> > On Wed, 22 Dec 2021, Jiufu Guo wrote: > >> > > >> >> Hi, > >> >> ... > >> >> > >> >> Bootstrap and regtest pass on ppc64* and x86

Re: [PATCH] disable aggressive_loop_optimizations until niter ready

2022-01-13 Thread Jiufu Guo via Gcc-patches
Richard Biener writes: > On Thu, 13 Jan 2022, guojiufu wrote: > >> On 2022-01-03 22:30, Richard Biener wrote: >> > On Wed, 22 Dec 2021, Jiufu Guo wrote: >> > >> >> Hi, >> >> ... >> >> >> >> Bootstrap and regtest pass on ppc64* and x86_64. Is this ok for trunk? >> > >> > So this is a optimalit

Re: [PATCH] disable aggressive_loop_optimizations until niter ready

2022-01-13 Thread Richard Biener via Gcc-patches
On Thu, 13 Jan 2022, guojiufu wrote: > On 2022-01-03 22:30, Richard Biener wrote: > > On Wed, 22 Dec 2021, Jiufu Guo wrote: > > > >> Hi, > >> > >> Normaly, estimate_numbers_of_iterations get/caculate niter first, > >> and then invokes infer_loop_bounds_from_undefined. While in some case, > >> af

Re: [PATCH] disable aggressive_loop_optimizations until niter ready

2022-01-13 Thread guojiufu via Gcc-patches
On 2022-01-03 22:30, Richard Biener wrote: On Wed, 22 Dec 2021, Jiufu Guo wrote: Hi, Normaly, estimate_numbers_of_iterations get/caculate niter first, and then invokes infer_loop_bounds_from_undefined. While in some case, after a few call stacks, estimate_numbers_of_iterations is invoked befo

Re: [PATCH] disable aggressive_loop_optimizations until niter ready

2022-01-03 Thread Richard Biener via Gcc-patches
On Wed, 22 Dec 2021, Jiufu Guo wrote: > Hi, > > Normaly, estimate_numbers_of_iterations get/caculate niter first, > and then invokes infer_loop_bounds_from_undefined. While in some case, > after a few call stacks, estimate_numbers_of_iterations is invoked before > niter is ready (e.g. before numb

[PATCH] disable aggressive_loop_optimizations until niter ready

2021-12-21 Thread Jiufu Guo via Gcc-patches
Hi, Normaly, estimate_numbers_of_iterations get/caculate niter first, and then invokes infer_loop_bounds_from_undefined. While in some case, after a few call stacks, estimate_numbers_of_iterations is invoked before niter is ready (e.g. before number_of_latch_executions returns). e.g. number_of_la