public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/98003] New: FAIL: 27_io/basic_syncbuf/sync_ops/1.cc (test for excess errors) Date: Thu, 26 Nov 2020 10:28:21 +0000 [thread overview] Message-ID: <bug-98003-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98003 Bug ID: 98003 Summary: FAIL: 27_io/basic_syncbuf/sync_ops/1.cc (test for excess errors) Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: redi at gcc dot gnu.org CC: danglin at gcc dot gnu.org Target Milestone: --- Target: hppa64-hp-hpux11.11 https://gcc.gnu.org/pipermail/gcc-testresults/2020-November/630265.html
next reply other threads:[~2020-11-26 10:28 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-26 10:28 redi at gcc dot gnu.org [this message] 2020-11-30 22:11 ` [Bug libstdc++/98003] " danglin at gcc dot gnu.org 2020-11-30 22:24 ` redi at gcc dot gnu.org 2020-12-01 10:38 ` cvs-commit at gcc dot gnu.org 2020-12-01 10:39 ` redi at gcc dot gnu.org 2020-12-12 16:58 ` dave.anglin at bell dot net
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=bug-98003-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).