On 12/11/14 14:56 +, Christopher Jefferson wrote:
I did suggest this change, so I feel I should defend it!
Our testing of many algorithms is woefully slim, that is how (for
example) the segfaulting bug in std::nth_element got through into a
release -- the tests for that algorithm were terrib
I did suggest this change, so I feel I should defend it!
Our testing of many algorithms is woefully slim, that is how (for
example) the segfaulting bug in std::nth_element got through into a
release -- the tests for that algorithm were terrible, and basically
didn't test the functionality on enoug
On 10/11/14 23:39 +0100, François Dumont wrote:
No the random tests didn't show any problem. I had demonstrated the
problems with the modifications on the existing tests simulating
constraint memory context.
So unless specified otherwise I will commit tomorrow without the tests
using random n
No the random tests didn't show any problem. I had demonstrated the
problems with the modifications on the existing tests simulating
constraint memory context.
So unless specified otherwise I will commit tomorrow without the tests
using random numbers.
François
On 10/11/2014 23:20, Jonatha
On 10/11/14 23:14 +0100, François Dumont wrote:
I introduced the random tests after Christopher Jefferson request
to have more intensive tests on those algos. Is it the whole stuff of
tests using random numbers that you don't like or just the usage of
mt19937 ?
The use of random number in
I introduced the random tests after Christopher Jefferson request
to have more intensive tests on those algos. Is it the whole stuff of
tests using random numbers that you don't like or just the usage of
mt19937 ? If second is this new version using the usual random_device I
used so far bet
On 10/11/14 21:50 +0100, François Dumont wrote:
Any news about this one ?
Here is another version with additional random tests on algos just to
challenge other combinations of tests.
PR libstdc++/61107
* include/bits/stl_algo.h (__inplace_stable_partition): Delete.
(__stable_partitio
Any news about this one ?
Here is another version with additional random tests on algos just to
challenge other combinations of tests.
PR libstdc++/61107
* include/bits/stl_algo.h (__inplace_stable_partition): Delete.
(__stable_partition_adaptive): Return __first is range length is
Hi
As proposed in the bug report I just removed the
__inplace_stable_partition as __stable_partition_adaptive is able to
handle a 0 buffer size.
To test this bug I introduced overloads of new/delete operators in
the testsuite utils. The existing set_memory_limits has no impact on new
