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++/99995] [11 Regression] should not include <unistd.h> in c++20 mode
Date: Mon, 12 Apr 2021 10:37:54 +0000 [thread overview]
Message-ID: <bug-99995-4-QOX64gpu83@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99995-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99995
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Last reconfirmed| |2021-04-12
Status|UNCONFIRMED |SUSPENDED
Summary|[11 Regression] FAIL: |[11 Regression] should not
|17_intro/headers/c++1998/49 |include <unistd.h> in c++20
|745.cc with -std=gnu++20 |mode
Target Milestone|11.0 |12.0
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I've done the XFAIL. Removing the <unistd.h> dependency isn't going to happen
for GCC 11.
next prev parent reply other threads:[~2021-04-12 10:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 13:25 [Bug libstdc++/99995] New: [11 Regression] FAIL: 17_intro/headers/c++1998/49745.cc with -std=gnu++20 redi at gcc dot gnu.org
2021-04-12 7:41 ` [Bug libstdc++/99995] " rguenth at gcc dot gnu.org
2021-04-12 10:35 ` cvs-commit at gcc dot gnu.org
2021-04-12 10:37 ` redi at gcc dot gnu.org [this message]
2021-04-21 12:06 ` [Bug libstdc++/99995] [11/12 Regression] should not include <unistd.h> in c++20 mode redi at gcc dot gnu.org
2022-05-06 8:30 ` [Bug libstdc++/99995] [11/12/13 " jakub at gcc dot gnu.org
2023-05-08 12:21 ` [Bug libstdc++/99995] [11/12/13/14 " 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-99995-4-QOX64gpu83@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: 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).