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 r13-8158] libstdc++: Add dg-output to two tests Date: Fri, 15 Dec 2023 11:33:31 +0000 (GMT) [thread overview] Message-ID: <20231215113331.078D938708C1@sourceware.org> (raw) https://gcc.gnu.org/g:2316fe2790416635d7dfc994ae4ef97280c9da89 commit r13-8158-g2316fe2790416635d7dfc994ae4ef97280c9da89 Author: Jonathan Wakely <jwakely@redhat.com> Date: Mon Dec 11 22:58:46 2023 +0000 libstdc++: Add dg-output to two tests These tests are expected to run interactively, with the output checked by eye. Nobody ever does that, but we can at least use dg-output to check that the output is as expected. libstdc++-v3/ChangeLog: * testsuite/27_io/objects/char/2.cc: Use dg-output. * testsuite/27_io/objects/wchar_t/2.cc: Use dg-output. (cherry picked from commit 0c773209fc9d0b5fa04f4055bdc2ff9746a1999d) Diff: --- libstdc++-v3/testsuite/27_io/objects/char/2.cc | 2 ++ libstdc++-v3/testsuite/27_io/objects/wchar_t/2.cc | 2 ++ 2 files changed, 4 insertions(+) diff --git a/libstdc++-v3/testsuite/27_io/objects/char/2.cc b/libstdc++-v3/testsuite/27_io/objects/char/2.cc index b6c49bac6f3..9026a3cbad8 100644 --- a/libstdc++-v3/testsuite/27_io/objects/char/2.cc +++ b/libstdc++-v3/testsuite/27_io/objects/char/2.cc @@ -38,6 +38,8 @@ void test04() cout.flush(); } +// { dg-output "hello fine world" } + int main() { diff --git a/libstdc++-v3/testsuite/27_io/objects/wchar_t/2.cc b/libstdc++-v3/testsuite/27_io/objects/wchar_t/2.cc index 52a21b8dc22..2e47aba7c3c 100644 --- a/libstdc++-v3/testsuite/27_io/objects/wchar_t/2.cc +++ b/libstdc++-v3/testsuite/27_io/objects/wchar_t/2.cc @@ -38,6 +38,8 @@ void test04() wcout.flush(); } +// { dg-output "hello fine world" } + int main() {
reply other threads:[~2023-12-15 11:33 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=20231215113331.078D938708C1@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).