Re: Fix PR 86979

2019-03-18 Thread Jakub Jelinek
On Fri, Mar 15, 2019 at 01:25:57PM +0300, Andrey Belevantsev wrote: > 2019-03-15 Andrey Belevantsev > > PR middle-end/89676 There is a typo in the PR number that I've fixed and added a testcase for this, committed as obvious: 2019-03-18 Jakub Jelinek PR middle-end/86979

Re: Fix PR 86979

2019-03-15 Thread Jakub Jelinek
On Fri, Mar 15, 2019 at 02:27:35PM +0300, Alexander Monakov wrote: > On Fri, 15 Mar 2019, Jakub Jelinek wrote: > > > On Fri, Mar 15, 2019 at 01:25:57PM +0300, Andrey Belevantsev wrote: > > > As explained in the PR trail, we incorrectly update the availability sets > > > in the rare case of several

Re: Fix PR 86979

2019-03-15 Thread Alexander Monakov
On Fri, 15 Mar 2019, Jakub Jelinek wrote: > On Fri, Mar 15, 2019 at 01:25:57PM +0300, Andrey Belevantsev wrote: > > As explained in the PR trail, we incorrectly update the availability sets > > in the rare case of several successors and one of them having another > > fence. Fixed as follows. Ok

Re: Fix PR 86979

2019-03-15 Thread Jakub Jelinek
On Fri, Mar 15, 2019 at 01:25:57PM +0300, Andrey Belevantsev wrote: > As explained in the PR trail, we incorrectly update the availability sets > in the rare case of several successors and one of them having another > fence. Fixed as follows. Ok for trunk? > > Best, > Andrey > > 2019-03-15 And

Fix PR 86979

2019-03-15 Thread Andrey Belevantsev
Hello, As explained in the PR trail, we incorrectly update the availability sets in the rare case of several successors and one of them having another fence. Fixed as follows. Ok for trunk? Best, Andrey 2019-03-15 Andrey Belevantsev PR middle-end/89676 * sel-sched.c (comput