From: Alexandre Oliva <oliva@adacore.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: Sebastian Huber <sebastian.huber@embedded-brains.de>,
"libstdc++" <libstdc++@gcc.gnu.org>,
gcc Patches <gcc-patches@gcc.gnu.org>, RTEMS <devel@rtems.org>
Subject: Re: [PATCH] libstdc++: testsuite: fs rename to self may fail
Date: Thu, 23 Jun 2022 00:59:14 -0300 [thread overview]
Message-ID: <or8rpo6ne5.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <CACb0b4kBZYTgxUrxz5HEZVpJin6TAULKOTiU62sjZAh66QXVng@mail.gmail.com> (Jonathan Wakely's message of "Wed, 22 Jun 2022 11:41:14 +0100")
On Jun 22, 2022, Jonathan Wakely <jwakely@redhat.com> wrote:
> On Wed, 22 Jun 2022 at 08:02, Alexandre Oliva via Libstdc++
> <libstdc++@gcc.gnu.org> wrote:
>>
>> Hello, Sebastian,
>>
>> On Jun 22, 2022, Sebastian Huber <sebastian.huber@embedded-brains.de> wrote:
>>
>> > On 22/06/2022 08:24, Alexandre Oliva via Libstdc++ wrote:
>> >> rtems6's rename() implementation errors with EEXIST when the rename-to
>> >> filename exists, even when renaming a file to itself or when renaming
>> >> a nonexisting file. Adjust expectations.
>> >>
>> >> Regstrapped on x86_64-linux-gnu, also tested with a cross to
>> >> aarch64-rtems6. Ok to install?
>> >>
>> >> PS:https://devel.rtems.org/ticket/2169 doesn't seem to suggest plans to
>> >> change behavior so as to comply with POSIX.
>>
>> > I would not adjust the test case to cope with systems which are not in
>> > line with POSIX.
>>
>> My understanding is that the libstdc++ testsuite is not meant to test
>> for POSIX conformance, but for conformance with the C++ language
>> standards.
>>
>> C++ inherits rename from C, and C says the behavior is implementation
>> defined if the new name already exists.
> std::filesystem::rename is explicitly specified in terms of POSIX
> rename, not C rename.
Oh, sorry, I stand corrected. I meant ::rename only. My mind seems to
still resist the notion that <filesystem> is standard C++, rather than
an experimental extension proposal :-)
Anyway, I did not realize it deferred to POSIX semantics, even when
that's stricter than C standard. Interesting...
> Instead, the implementation of std::filesystem::rename should have a
> special-case for rtems (and maybe other targets) that implements the
> POSIX rename semantics if calling ::rename isn't good enough.
Given what I've just learned, I agree. Patch withdrawn. I suppose the
other patch, on subdir renaming, must share the same fate.
/me longs for XFAILs for libstdc++ subtests ;-)
--
Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
Free Software Activist GNU Toolchain Engineer
Disinformation flourishes because many people care deeply about injustice
but very few check the facts. Ask me about <https://stallmansupport.org>
next prev parent reply other threads:[~2022-06-23 3:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 6:24 Alexandre Oliva
2022-06-22 6:33 ` Sebastian Huber
2022-06-22 7:01 ` Alexandre Oliva
2022-06-22 10:41 ` Jonathan Wakely
2022-06-23 3:59 ` Alexandre Oliva [this message]
2022-06-23 6:26 ` Alexandre Oliva
2022-06-23 9:25 ` Jonathan Wakely
2022-06-23 11:21 ` Alexandre Oliva
2022-06-23 11:38 ` Jonathan Wakely
2022-06-23 12:41 ` 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=or8rpo6ne5.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=devel@rtems.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=sebastian.huber@embedded-brains.de \
/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: link
Be 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).