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:32 +0000 [thread overview]
Message-ID: <bug-103626-4-RpM8gBJzSB@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 #7 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:f1b51f68f8ac6c63e352dda8599aed01634212de
commit r13-3034-gf1b51f68f8ac6c63e352dda8599aed01634212de
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Tue Sep 20 11:57:28 2022 +0100
libstdc++: Make _GLIBCXX_HOSTED respect -ffreestanding [PR103626]
This allows the library to switch to freestanding mode when compiling
with the -ffreestanding flag. This means you don't need a separate
libstdc++ build configured with --disable-hosted-libstdcxx in order to
compile for a freestanding environment.
The testsuite support files cannot be compiled for freestanding, so add
-fno-freestanding to override any -ffreestanding in the test flags.
libstdc++-v3/ChangeLog:
PR libstdc++/103626
* acinclude.m4 (GLIBCXX_ENABLE_HOSTED): Define _GLIBCXX_HOSTED
to __STDC_HOSTED__ for non-freestanding installations.
* configure: Regenerate.
* include/Makefile.am (${host_builddir}/c++config.h): Adjust
grep pattern.
* include/Makefile.in: Regenerate.
* testsuite/lib/libstdc++.exp (v3-build_support): Use
-fno-freestanding.
* testsuite/libstdc++-abi/abi.exp: 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 [this message]
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: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-RpM8gBJzSB@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).