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 successors and one of them having another > > > fence. Fixed as follows. Ok for trunk? > > > > > > Best, > > > Andrey > > > > > > 2019-03-15 Andrey Belevantsev <a...@ispras.ru> > > > > > > PR middle-end/89676 > > > * sel-sched.c (compute_av_set_at_bb_end): When we have an ineligible > > > successor, > > > use NULL as its av set. > > > > Just formatting nits, will defer actual review to some scheduler maintainer. > > I can do this, it falls under sel-sched maintenance and Andrey showed to me > in person the algorithmic corner-case here, so: OK for trunk with formatting > fixed.
Can you please update MAINTAINERS for you then (and Dmitry too)? In https://gcc.gnu.org/ml/gcc/2011-11/msg00264.html you are listed all 3, but only Abel has added himself to selective scheduling in MAINTAINERS in r181284. Jakub
