Re: Backporting gcc_qsort

2018-10-01 Thread Cory Fields
Understood. Thank you for the explanations. I'll just plan to apply the patches locally as well. Regards, Cory On Mon, Oct 1, 2018 at 11:18 AM Alexander Monakov wrote: > > On Mon, 1 Oct 2018, Jeff Law wrote: > > To add a bit more context for Cory. > > > > Generally backports are limited to fixin

Re: Backporting gcc_qsort

2018-10-01 Thread Alexander Monakov
On Mon, 1 Oct 2018, Jeff Law wrote: > To add a bit more context for Cory. > > Generally backports are limited to fixing regressions and serious code > generation bugs. While we do make some exceptions, those are good > general guidelines. > > I don't think the qsort changes warrant an exception.

Re: Backporting gcc_qsort

2018-10-01 Thread Jeff Law
On 10/1/18 2:20 AM, Richard Biener wrote: > On Fri, Sep 28, 2018 at 7:08 PM Cory Fields wrote: >> >> gcc_qsort as introduced by Alexander Monakov [0] in trunk for 9.x is a >> great change that defines the order of otherwise-unbalanced internal >> sorts, some of which would otherwise cause bootstra

Re: Backporting gcc_qsort

2018-10-01 Thread Richard Biener
On Fri, Sep 28, 2018 at 7:08 PM Cory Fields wrote: > > gcc_qsort as introduced by Alexander Monakov [0] in trunk for 9.x is a > great change that defines the order of otherwise-unbalanced internal > sorts, some of which would otherwise cause bootstrapping failures. > > I would like to request that

Backporting gcc_qsort

2018-09-28 Thread Cory Fields
gcc_qsort as introduced by Alexander Monakov [0] in trunk for 9.x is a great change that defines the order of otherwise-unbalanced internal sorts, some of which would otherwise cause bootstrapping failures. I would like to request that these it as well as subsequent fixups (all listed specifically