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++/103626] New: _GLIBCXX_HOSTED should respect -ffreestanding
Date: Thu, 09 Dec 2021 11:05:34 +0000 [thread overview]
Message-ID: <bug-103626-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103626
Bug ID: 103626
Summary: _GLIBCXX_HOSTED should respect -ffreestanding
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
Blocks: 19992
Target Milestone: ---
Libstdc++ should not define _GLIBCXX_HOSTED to 1 when __STD_HOSTED__ == 0 i.e.
when -ffreestanding is used.
This will allow -ffreestanding to affect the library as well as the compiler,
avoiding the need to build and install a separate libstdc++ to get a
freestanding implementation.
The --disable-hosted-libstdcxx configure option will still allow installation
of a library that can never be used as hosted, but it will also be possible to
use an existing hosted implementation in freestanding mode.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19992
[Bug 19992] -fhosted/-ffreestanding for C++
next reply other threads:[~2021-12-09 11:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-09 11:05 redi at gcc dot gnu.org [this message]
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
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@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).