From: Alexander Monakov <amonakov@ispras.ru>
To: Franz Sirl <Franz.Sirl-kernel@lauterbach.com>
Cc: Jeff Law <law@redhat.com>, GCC Patches <gcc-patches@gcc.gnu.org>,
Martin Jambor <mjambor@suse.cz>
Subject: Re: [RFC][PATCH] Stabilize a few qsort comparison functions
Date: Wed, 13 Jun 2018 12:47:00 -0000 [thread overview]
Message-ID: <alpine.LNX.2.20.13.1806131535260.7678@monopod.intra.ispras.ru> (raw)
In-Reply-To: <ce3c46bb-57cf-bbb7-d965-c23e8e5c5b65@lauterbach.com>
On Wed, 13 Jun 2018, Franz Sirl wrote:
> So, unless someone thinks one of the changes makes sense anyway, this patch is
> obsolete.
Yeah, I think that in light of gcc_qsort work this patch is completely
unnecessary now, and shouldn't be applied. In fact, reversing earlier
artificial stabilization changes may be desirable.
Alexander
next prev parent reply other threads:[~2018-06-13 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 16:58 Franz Sirl
2018-02-08 15:33 ` Martin Jambor
2018-06-12 21:49 ` Jeff Law
2018-06-13 11:50 ` Franz Sirl
2018-06-13 12:47 ` Alexander Monakov [this message]
2018-06-13 19:26 ` Jeff Law
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LNX.2.20.13.1806131535260.7678@monopod.intra.ispras.ru \
--to=amonakov@ispras.ru \
--cc=Franz.Sirl-kernel@lauterbach.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=mjambor@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).