Re: [PATCH 5/4] tree-optimization/104288 - An alternative approach

2022-02-08 Thread Andrew MacLeod via Gcc-patches
On 2/8/22 03:32, Richard Biener wrote: On Tue, Feb 8, 2022 at 2:33 AM Andrew MacLeod via Gcc-patches wrote: On 2/7/22 09:29, Andrew MacLeod wrote: I have a proposal for PR 104288. ALL patches (in sequence) bootstrap on their own and each cause no regressions. I've been continuing to work wit

Re: [PATCH 5/4] tree-optimization/104288 - An alternative approach

2022-02-08 Thread Andrew MacLeod via Gcc-patches
On 2/8/22 03:32, Richard Biener wrote: On Tue, Feb 8, 2022 at 2:33 AM Andrew MacLeod via Gcc-patches wrote: On 2/7/22 09:29, Andrew MacLeod wrote: I have a proposal for PR 104288. ALL patches (in sequence) bootstrap on their own and each cause no regressions. I've been continuing to work wit

Re: [PATCH 5/4] tree-optimization/104288 - An alternative approach

2022-02-08 Thread Richard Biener via Gcc-patches
On Tue, Feb 8, 2022 at 2:33 AM Andrew MacLeod via Gcc-patches wrote: > > On 2/7/22 09:29, Andrew MacLeod wrote: > > I have a proposal for PR 104288. > > > > ALL patches (in sequence) bootstrap on their own and each cause no > > regressions. > > I've been continuing to work with this towards the GC

[PATCH 5/4] tree-optimization/104288 - An alternative approach

2022-02-07 Thread Andrew MacLeod via Gcc-patches
On 2/7/22 09:29, Andrew MacLeod wrote: I have a proposal for PR 104288. ALL patches (in sequence) bootstrap on their own and each cause no regressions. I've been continuing to work with this towards the GCC13 solution for statement side effects.  And There is another possibility we could pu