public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc(refs/users/aoliva/heads/testme)] libstdc++: xfail rename tests on rtems Date: Thu, 23 Jun 2022 12:06:24 +0000 (GMT) [thread overview] Message-ID: <20220623120624.D287B3856DF8@sourceware.org> (raw) https://gcc.gnu.org/g:ea68fd776e25862b0674e2f6403d4708d125cb40 commit ea68fd776e25862b0674e2f6403d4708d125cb40 Author: Alexandre Oliva <oliva@adacore.com> Date: Thu Jun 23 04:12:22 2022 -0300 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. Diff: --- libstdc++-v3/testsuite/27_io/filesystem/operations/rename.cc | 1 + libstdc++-v3/testsuite/experimental/filesystem/operations/rename.cc | 1 + 2 files changed, 2 insertions(+) diff --git a/libstdc++-v3/testsuite/27_io/filesystem/operations/rename.cc b/libstdc++-v3/testsuite/27_io/filesystem/operations/rename.cc index b74e1133a76..983374f42e4 100644 --- a/libstdc++-v3/testsuite/27_io/filesystem/operations/rename.cc +++ b/libstdc++-v3/testsuite/27_io/filesystem/operations/rename.cc @@ -17,6 +17,7 @@ // { dg-do run { target c++17 } } // { dg-require-filesystem-ts "" } +// { dg-xfail-run-if "rename is not POSIX-compliant" { *-*-rtems* } } #include <filesystem> #include <testsuite_hooks.h> diff --git a/libstdc++-v3/testsuite/experimental/filesystem/operations/rename.cc b/libstdc++-v3/testsuite/experimental/filesystem/operations/rename.cc index 37e743b770f..762b943888f 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>
next reply other threads:[~2022-06-23 12:06 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-23 12:06 Alexandre Oliva [this message] -- strict thread matches above, loose matches on Subject: below -- 2022-06-23 14:02 Alexandre Oliva 2022-06-23 12:44 Alexandre Oliva 2022-06-23 12:30 Alexandre Oliva 2022-06-23 12:22 Alexandre Oliva 2022-06-23 10:06 Alexandre Oliva 2022-06-23 9:02 Alexandre Oliva 2022-06-23 8:39 Alexandre Oliva 2022-06-23 7:15 Alexandre Oliva
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20220623120624.D287B3856DF8@sourceware.org \ --to=aoliva@gcc.gnu.org \ --cc=gcc-cvs@gcc.gnu.org \ --cc=libstdc++-cvs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).