From: Alexandre Oliva <oliva@adacore.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: Joel Brobecker <brobecker@adacore.com>,
gcc Patches <gcc-patches@gcc.gnu.org>,
"libstdc++" <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH] libstdc++: testsuite: avoid predictable mkstemp
Date: Tue, 05 Jul 2022 06:10:22 -0300 [thread overview]
Message-ID: <ory1x8orgh.fsf@lxoliva.fsfla.org> (raw)
In-Reply-To: <orr13azc3e.fsf@lxoliva.fsfla.org> (Alexandre Oliva's message of "Mon, 27 Jun 2022 06:31:49 -0300")
On Jun 27, 2022, Alexandre Oliva <oliva@adacore.com> wrote:
> On Jun 23, 2022, Jonathan Wakely <jwakely@redhat.com> wrote:
>> The attached makes this a bit more efficient, and makes more of the
>> code common to the mkstemp and non-mkstmp branches. I'll wait to hear
>> back from you before pushing it (since it has Joel's name on the
>> patch).
> Thanks, I've given it a spin, both trunk and gcc-11, and I confirm it
> works for us.
The bad news is that it broke on some other systems I didn't test back
then. It turns out the type cast for the ::getpid result was not just
because it was passed to printf before :-/
libstdc++: testsuite: cast getpid result
On vxworks, in kernel mode, getpid's return type is a pointer type, so
std::to_string on it fails overload resolution. Restore the type cast
from the original patch that suggested adding the pid.
Regstrapped on x86_64-linux-gnu, also tested on aarch64-rtems6.0 and
ppc64-vx7r2. I'm going ahead and checking this in as obvious. Please
let me know if you'd prefer this to be fixed in a different way.
for libstdc++/ChangeLog
* testsuite/util/testsuite_fs.h (nonexistent_path): Convert
the getpid result to an integral type.
---
libstdc++-v3/testsuite/util/testsuite_fs.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libstdc++-v3/testsuite/util/testsuite_fs.h b/libstdc++-v3/testsuite/util/testsuite_fs.h
index 908fcdbcaeed1..25f8f734dc792 100644
--- a/libstdc++-v3/testsuite/util/testsuite_fs.h
+++ b/libstdc++-v3/testsuite/util/testsuite_fs.h
@@ -163,7 +163,7 @@ namespace __gnu_test
file.resize(64);
// The combination of random counter and PID should be unique for a given
// run of the testsuite.
- file += std::to_string(::getpid());
+ file += std::to_string((unsigned long) ::getpid());
p = std::move(file);
if (test_fs::exists(p))
throw test_fs::filesystem_error("Failed to generate unique pathname", p,
--
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-07-05 9:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 6:04 Alexandre Oliva
2022-06-22 9:16 ` Jonathan Wakely
2022-06-23 11:39 ` Alexandre Oliva
2022-06-23 16:36 ` Jonathan Wakely
2022-06-27 9:31 ` Alexandre Oliva
2022-06-27 10:18 ` Jonathan Wakely
2022-07-05 9:10 ` Alexandre Oliva [this message]
2022-07-05 9:16 ` Jonathan Wakely
2022-07-05 17:45 ` Alexandre Oliva
2022-07-05 18:02 ` Jonathan Wakely
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=ory1x8orgh.fsf@lxoliva.fsfla.org \
--to=oliva@adacore.com \
--cc=brobecker@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@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: 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).