public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/98319] LFTS headers give errors if included as C++11 or C++98 Date: Mon, 29 Mar 2021 20:02:04 +0000 [thread overview] Message-ID: <bug-98319-4-sLSY966N9b@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98319-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98319 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:564e5b6ce002608f461d4275c126d8179ef806c6 commit r10-9578-g564e5b6ce002608f461d4275c126d8179ef806c6 Author: Jonathan Wakely <jwakely@redhat.com> Date: Wed Dec 16 13:37:17 2020 +0000 libstdc++: Fix errors from Library Fundamentals TS headers in C++11 [PR 98319] Currently the <experimental/random>, <experimental/source_location> and <experimental/utility> headers can be included in C++98 and C++11 modes, but gives errors. With this change they can be included, but define nothing. libstdc++-v3/ChangeLog: PR libstdc++/98319 * include/experimental/random: Only define contents for C++14 and later. * include/experimental/source_location: Likewise. * include/experimental/utility: Likewise. * testsuite/experimental/feat-lib-fund.cc: Include all LFTS headers that are present. Allow test to run for all modes. (cherry picked from commit ab9bd93271061f436c10e35e261ecb73e2108ccc)
next prev parent reply other threads:[~2021-03-29 20:02 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-16 12:25 [Bug libstdc++/98319] New: " redi at gcc dot gnu.org 2020-12-16 12:25 ` [Bug libstdc++/98319] " redi at gcc dot gnu.org 2020-12-16 13:37 ` cvs-commit at gcc dot gnu.org 2020-12-16 13:55 ` redi at gcc dot gnu.org 2021-03-29 20:02 ` cvs-commit at gcc dot gnu.org [this message] 2021-03-29 20:04 ` redi at gcc dot gnu.org 2021-04-19 9:31 ` cvs-commit at gcc dot gnu.org 2021-04-19 9:38 ` cvs-commit at gcc dot gnu.org 2021-04-19 9:39 ` redi at gcc dot gnu.org 2021-09-11 14:29 ` pinskia 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-98319-4-sLSY966N9b@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).