public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc r9-9074] libstdc++: Fix undefined FILE* operations in test Date: Thu, 26 Nov 2020 12:05:28 +0000 (GMT) [thread overview] Message-ID: <20201126120528.62C6C396EC9E@sourceware.org> (raw) https://gcc.gnu.org/g:e45e65016754cf4bfc6c00cbbdca700f01f7c324 commit r9-9074-ge45e65016754cf4bfc6c00cbbdca700f01f7c324 Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Nov 26 11:25:55 2020 +0000 libstdc++: Fix undefined FILE* operations in test We only need to check that the constructor doesn't clear errno, so there's no need to use an invalid FILE* for that. libstdc++-v3/ChangeLog: PR libstdc++/98001 * testsuite/ext/stdio_filebuf/char/79820.cc: Do not pass invalid FILE* to constructor. (cherry picked from commit 2762cb1df686fc1ebcee23c7c4f0f6e8bf5a6abc) Diff: --- libstdc++-v3/testsuite/ext/stdio_filebuf/char/79820.cc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/libstdc++-v3/testsuite/ext/stdio_filebuf/char/79820.cc b/libstdc++-v3/testsuite/ext/stdio_filebuf/char/79820.cc index e16cddc1ea4..03f95d3c265 100644 --- a/libstdc++-v3/testsuite/ext/stdio_filebuf/char/79820.cc +++ b/libstdc++-v3/testsuite/ext/stdio_filebuf/char/79820.cc @@ -26,10 +26,11 @@ void test01() { FILE* f = std::fopen("79820.txt", "w"); - std::fclose(f); errno = 127; __gnu_cxx::stdio_filebuf<char> b(f, std::ios::out, BUFSIZ); VERIFY(errno == 127); // PR libstdc++/79820 + b.close(); + std::fclose(f); } int
reply other threads:[~2020-11-26 12:05 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20201126120528.62C6C396EC9E@sourceware.org \ --to=redi@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).