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++/100117] FAIL testsuite/17_intro/headers/c++1998/49745.cc with trunk glibc Date: Fri, 16 Apr 2021 19:00:34 +0000 [thread overview] Message-ID: <bug-100117-4-NFHVWaeink@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100117-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100117 Jonathan Wakely <redi at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=99995 --- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> --- <bits/stdc++.h> includes all standard headers, including <csignal>. Maybe for the purposes of that test, what we should really check is that none of the C++ headers (i.e. all except <foo.h> and <cfoo>) includes <unistd.h>.
next prev parent reply other threads:[~2021-04-16 19:00 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-16 14:13 [Bug libstdc++/100117] New: " jakub at gcc dot gnu.org 2021-04-16 14:38 ` [Bug libstdc++/100117] " fw at gcc dot gnu.org 2021-04-16 14:46 ` jakub at gcc dot gnu.org 2021-04-16 14:59 ` fw at gcc dot gnu.org 2021-04-16 19:00 ` redi at gcc dot gnu.org [this message] 2021-08-13 22:22 ` slyfox at gcc dot gnu.org 2021-11-10 12:04 ` cvs-commit at gcc dot gnu.org 2021-11-10 12:05 ` redi at gcc dot gnu.org 2021-11-24 11:50 ` cvs-commit at gcc dot gnu.org 2022-04-26 13:12 ` cvs-commit at gcc dot gnu.org 2022-05-27 9:03 ` rguenth at gcc dot gnu.org
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-100117-4-NFHVWaeink@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).