On 12/06/2017 13:57, Jonathan Wakely wrote:
Ok to commit ?
OK, thanks.
Done yesterday.
I guess that considering the compiler bug and rare occasions for this
bug to show up we don't backport.
François
On 10/06/17 16:44 +0200, François Dumont wrote:
On 08/06/2017 15:22, Jonathan Wakely wrote:
Can't we just have one file per container type (maybe just called
default_init.cc) which tests default-initialization in test01() and
value-initialization in a test02() function?
While working on this we
On 08/06/2017 15:22, Jonathan Wakely wrote:
Oh dear, we have a compiler bug:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65816
And not a recent one !
which takes place only if I call this:
test_type *tmp = ::new(buf._M_addr()) test_type {};
To force default/value init looks like gcc forc
On 07/06/17 22:44 +0200, François Dumont wrote:
On 05/06/2017 13:31, Jonathan Wakely wrote:
On 04/06/17 22:26 +0200, François Dumont wrote:
Hi
I have eventually adapt the test to all containers and the
result is successful for map/set/unordered_map/unordered_set. It
is failing for deque/li
On 05/06/2017 13:31, Jonathan Wakely wrote:
On 04/06/17 22:26 +0200, François Dumont wrote:
Hi
I have eventually adapt the test to all containers and the result
is successful for map/set/unordered_map/unordered_set. It is failing
for deque/list/forward_list/vector/vector.
I even try t
On 04/06/17 22:26 +0200, François Dumont wrote:
Hi
I have eventually adapt the test to all containers and the result
is successful for map/set/unordered_map/unordered_set. It is failing
for deque/list/forward_list/vector/vector.
I even try to change the test to look at the difference b
