On Sun, 2017-07-16 at 17:32 -0500, Segher Boessenkool wrote:
> On Sun, Jul 16, 2017 at 11:54:43PM +0300, Alexander Monakov wrote:
> >
> > On Sun, 16 Jul 2017, Segher Boessenkool wrote:
> > >
> > > I am well aware, and that is not what I asked. If we would use
> > > stable sorts everywhere
> > H
Snapshot gcc-8-20170716 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/8-20170716/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 8 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision
On Sun, Jul 16, 2017 at 11:54:43PM +0300, Alexander Monakov wrote:
> On Sun, 16 Jul 2017, Segher Boessenkool wrote:
> > I am well aware, and that is not what I asked. If we would use stable
> > sorts everywhere
>
> How? There's no stable sort in libc and switching over to std::stable_sort
> would
On Sun, 16 Jul 2017, Segher Boessenkool wrote:
> I am well aware, and that is not what I asked. If we would use stable
> sorts everywhere
How? There's no stable sort in libc and switching over to std::stable_sort
would be problematic. The obvious approach is adding an implementation of
a stable s
On Sun, Jul 16, 2017 at 12:38:58PM +0300, Alexander Monakov wrote:
> On Sat, 15 Jul 2017, Segher Boessenkool wrote:
> > Would it hurt us to use stable sorts *everywhere*?
>
> Stability (using the usual definition: keeping the original order of
> elements that compare equal) is not required to achi
Hi Bernd,
On Fri, Jul 14, 2017 at 4:36 PM, Bernd Edlinger
wrote:
> On 07/14/17 13:03, Georg-Johann Lay wrote:
>> On 13.07.2017 18:47, Bernd Edlinger wrote:
>>> On 07/13/17 16:31, Georg-Johann Lay wrote:
On 12.07.2017 15:40, Bernd Edlinger wrote:
> On 07/11/17 22:28, Bernd Edlinger wrote:
On Sat, 15 Jul 2017, Segher Boessenkool wrote:
> Would it hurt us to use stable sorts *everywhere*?
Stability (using the usual definition: keeping the original order of
elements that compare equal) is not required to achieve reproducibility [*].
GCC could import or nih any non-randomized implement