Re: [libstdc++-v3] Fix dg-require before dg-run directives in testsuite.

[Jonathan Wakely <jwakely@redhat.com>]

On 02/09/16 14:17 +0100, Matthew Wahab wrote:
>Hello,
>
>Tests in the libstdc++-v3 testsuite were recently changed to use { dg-do
>.. { target c++11 } } instead of using a dg-options to set -std
>(https://gcc.gnu.org/ml/libstdc++/2016-08/msg00102.html). As a
>consequence, several tests were left with directive lists that had
>dg-require preceding dg-do. This meant that some tests were run when
>they should have been skipped as unsupported. In particular, most of the
>23_algorithms/*/complexity.cc tests became FAIL on aarch64-none-elf
>
>This patch adjusts the tests so that the dg-requires come after the
>dg-do directives. The makes the tests that were previously
>FAIL/UNRESOLVED become UNSUPPORTED. It also makes UNSUPPORTED some tests
>that were PASS.
>
>The tests that move from FAIL/UNRESOLVED to UNSUPPORTED:
>
>- 22_locale/locale/cons/unicode.cc.
>- 25_algorithms/{pop_heap,push_heap,sort_heap}/complexity.c.
>
From PASS to UNSUPPORTED:
>
>- 23_containers/*/debug/60499.c
>- 23_containers/vector/debug/52433.c
>
>Tested by running the testsuite for cross-compiled aarch64-none-elf.
>
>Ok for trunk?

Yes, thanks for cleaning this up.