Many regressions in *_neg testcases

[Jonathan Wakely]

On 02/10/14 13:57 +0200, Paolo Carlini wrote:
>Hi,
>
>I'm seeing these regressions:
>
>Running target unix
>FAIL: 20_util/declval/requirements/1_neg.cc  (test for errors, line 2088)
>FAIL: 20_util/declval/requirements/1_neg.cc (test for excess errors)
>FAIL: 20_util/duration/literals/range.cc  (test for errors, line 799)
>FAIL: 20_util/duration/literals/range.cc (test for excess errors)
>FAIL: 20_util/duration/requirements/typedefs_neg1.cc  (test for errors, line 249)
>FAIL: 20_util/duration/requirements/typedefs_neg1.cc (test for excess errors)
>FAIL: 20_util/duration/requirements/typedefs_neg2.cc  (test for errors, line 250)
>FAIL: 20_util/duration/requirements/typedefs_neg2.cc (test for excess errors)
>FAIL: 20_util/duration/requirements/typedefs_neg3.cc  (test for errors, line 252)
>FAIL: 20_util/duration/requirements/typedefs_neg3.cc (test for excess errors)
>FAIL: 20_util/make_signed/requirements/typedefs_neg.cc  (test for errors, line 1717)
>FAIL: 20_util/make_signed/requirements/typedefs_neg.cc  (test for errors, line 1753)
>FAIL: 20_util/make_signed/requirements/typedefs_neg.cc (test for excess errors)
>FAIL: 20_util/make_unsigned/requirements/typedefs_neg.cc  (test for errors, line 1620)
>FAIL: 20_util/make_unsigned/requirements/typedefs_neg.cc  (test for errors, line 1656)
>FAIL: 20_util/make_unsigned/requirements/typedefs_neg.cc (test for excess errors)
>FAIL: 23_containers/array/tuple_interface/get_neg.cc  (test for errors, line 277)
>FAIL: 23_containers/array/tuple_interface/get_neg.cc  (test for errors, line 286)
>FAIL: 23_containers/array/tuple_interface/get_neg.cc  (test for errors, line 294)
>FAIL: 23_containers/array/tuple_interface/get_neg.cc (test for excess errors)
>FAIL: 23_containers/array/tuple_interface/tuple_element_neg.cc  (test for errors, line 325)
>FAIL: 23_containers/array/tuple_interface/tuple_element_neg.cc (test for excess errors)
>
>
>
>abundantly confirmed on testresults. I suspect Ed forgot to update the 
>expected dg-error lines together with his std::is_final patch.

Yep, the fix is approved, just waiting for it to go in:
https://gcc.gnu.org/ml/gcc-patches/2014-10/msg00139.html