diff options
| author | Alexandre Oliva <oliva@adacore.com> | 2022-06-23 23:20:52 -0300 |
|---|---|---|
| committer | Alexandre Oliva <oliva@gnu.org> | 2022-06-23 23:28:14 -0300 |
| commit | 5d8a5f04acec697c893e1c2263032bc01e2c2f2b (patch) | |
| tree | eafed37916899ee0579a38b54d979d809b785e50 /libstdc++-v3/testsuite/experimental/filesystem | |
| parent | f01cf5eaa06e72cf8e1e7d7f37b41f9d5eaf3e5c (diff) | |
| download | gcc-5d8a5f04acec697c893e1c2263032bc01e2c2f2b.zip gcc-5d8a5f04acec697c893e1c2263032bc01e2c2f2b.tar.gz gcc-5d8a5f04acec697c893e1c2263032bc01e2c2f2b.tar.bz2 | |
libstdc++: xfail rename tests on rtems
::rename on RTEMS does not meet several POSIX requirements, despite
compliance with C and C++ standards. ::std::filesystem::rename, in
turn, has requirements borrowed from POSIX, so it would have to be a
lot more than a simple wrapper around ::rename on RTEMS, and even then
fall short.
Until RTEMS reimplements ::rename for POSIX compliance, expect
filesystem rename tests to fail on it.
for libstdc++-v3/ChangeLog
* testsuite/27_io/filesystem/operations/rename.cc: xfail on
rtems.
* testsuite/experimental/filesystem/operations/rename.cc:
Likewise.
Diffstat (limited to 'libstdc++-v3/testsuite/experimental/filesystem')
| -rw-r--r-- | libstdc++-v3/testsuite/experimental/filesystem/operations/rename.cc | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/libstdc++-v3/testsuite/experimental/filesystem/operations/rename.cc b/libstdc++-v3/testsuite/experimental/filesystem/operations/rename.cc index 37e743b..762b943 100644 --- a/libstdc++-v3/testsuite/experimental/filesystem/operations/rename.cc +++ b/libstdc++-v3/testsuite/experimental/filesystem/operations/rename.cc @@ -18,6 +18,7 @@ // { dg-options "-DUSE_FILESYSTEM_TS -lstdc++fs" } // { dg-do run { target c++11 } } // { dg-require-filesystem-ts "" } +// { dg-xfail-run-if "rename is not POSIX-compliant" { *-*-rtems* } } #include <experimental/filesystem> #include <testsuite_hooks.h> |