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++/103626] _GLIBCXX_HOSTED should respect -ffreestanding
Date: Mon, 03 Oct 2022 14:45:58 +0000 [thread overview]
Message-ID: <bug-103626-4-BNKkOC9dqZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103626-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103626
--- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:
https://gcc.gnu.org/g:46eb2860942a29b40822570cb6625620f69ed30e
commit r13-3039-g46eb2860942a29b40822570cb6625620f69ed30e
Author: Arsen ArsenoviÄ <arsen@aarsen.me>
Date: Fri Sep 30 16:53:18 2022 +0200
libstdc++: Make some tests work on freestanding [PR103626]
PR libstdc++/103626 - _GLIBCXX_HOSTED should respect -ffreestanding
Co-authored-by: Jonathan Wakely <jwakely@redhat.com>
libstdc++-v3/ChangeLog:
PR libstdc++/103626
* testsuite/17_intro/headers/c++1998/stdc++.cc [!__STDC_HOSTED__]:
Do not include C headers that aren't valid for freestanding.
* testsuite/17_intro/tag_type_explicit_ctor.cc [!__STDC_HOSTED__]:
Do not test tag types that aren't defined for freestanding.
* testsuite/18_support/headers/cstdlib/functions_std.cc: Do not
check for std::getenv and std::system for freestanding.
* testsuite/17_intro/using_namespace_std_exp_neg.cc
[!__STDC_HOSTED__]:
Do not test hosted parts of the standard library.
* testsuite/17_intro/using_namespace_std_tr1_neg.cc
[!__STDC_HOSTED__]:
Likewise.
* testsuite/20_util/allocator_traits/members/rebind_alloc.cc
[!__STDC_HOSTED__]:
Likewise.
*
testsuite/20_util/allocator_traits/requirements/explicit_instantiation.cc
[!HOSTED]:
Likewise.
* testsuite/20_util/headers/bitset/synopsis.cc [!__STDC_HOSTED__]:
Likewise.
* testsuite/20_util/make_unsigned/requirements/typedefs_neg.cc
[!__STDC_HOSTED__]:
Likewise.
* testsuite/20_util/pointer_traits/requirements/typedefs.cc
[!__STDC_HOSTED__]:
Likewise.
* testsuite/20_util/tuple/cons/deduction.cc [!__STDC_HOSTED__]:
Likewise.
* testsuite/25_algorithms/move/93872.cc [!__STDC_HOSTED__]:
Likewise.
* testsuite/std/ranges/adaptors/100577.cc [!__STDC_HOSTED__]:
Likewise.
next prev parent reply other threads:[~2022-10-03 14:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 11:05 [Bug libstdc++/103626] New: " redi at gcc dot gnu.org
2022-09-16 20:06 ` [Bug libstdc++/103626] " redi at gcc dot gnu.org
2022-09-17 19:37 ` arsen at aarsen dot me
2022-09-17 22:19 ` redi at gcc dot gnu.org
2022-09-18 1:40 ` arsen at aarsen dot me
2022-09-18 6:41 ` redi at gcc dot gnu.org
2022-09-18 12:36 ` arsen at aarsen dot me
2022-10-03 14:45 ` cvs-commit at gcc dot gnu.org
2022-10-03 14:45 ` cvs-commit at gcc dot gnu.org
2022-10-03 14:45 ` cvs-commit at gcc dot gnu.org [this message]
2022-10-03 14:46 ` cvs-commit at gcc dot gnu.org
2022-10-03 14:46 ` cvs-commit at gcc dot gnu.org
2022-10-03 14:46 ` cvs-commit at gcc dot gnu.org
2022-10-03 14:50 ` redi 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-103626-4-BNKkOC9dqZ@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).