This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Backporting gcc_qsort
- From: Alexander Monakov <amonakov at ispras dot ru>
- To: Jeff Law <law at redhat dot com>
- Cc: Richard Biener <richard dot guenther at gmail dot com>, lists at coryfields dot com, GCC Development <gcc at gcc dot gnu dot org>
- Date: Mon, 1 Oct 2018 18:18:56 +0300 (MSK)
- Subject: Re: Backporting gcc_qsort
- References: <CAApLimg7SM-H1-YBZ0DNS=JswDicJjWYeMOjGsuOX7XKZM7dYg@mail.gmail.com> <CAFiYyc0ShYe9TdAM=YK-7HpSJxi3xoPXPCeN3MoGOc7hiTOwYw@mail.gmail.com> <9b37ff1b-b22f-5e42-2072-58e08cf2dcc7@redhat.com>
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.
Personally I think in this case there isn't a strong reason to backport, the
patch is fairly isolated, so individuals or companies that need it should have
no problem backporting it on their own. Previously, Franz Sirl reported back
in June they've used the patch to achieve matching output on their Linux-hosted
vs Cygwin-hosted cross-compilers based on GCC 8:
https://gcc.gnu.org/ml/gcc-patches/2018-06/msg00751.html
Alexander