From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B05F73AA8020; Sun, 18 Sep 2022 06:41:13 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B05F73AA8020 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1663483273; bh=MEr+ouxb80qlWd1MlKfnio1fJWzXxPEBJUP/1FK30Eg=; h=From:To:Subject:Date:In-Reply-To:References:From; b=GJduvnKR9uZ5OsgyLW0hEYocL/YXySPP3xwf/6AleW6+NZiWrBRDrZB2Eriq4Nba9 C7zW2s1YiCQR8vzXnnPIlFM04HquHF9qzhRafXSAf4BmYvePH0HMYe7VWygt7Bn4Cz OY0yxGl34kUbUmKwFl54N5cWHnn3XyGrwjbNtSgo= From: "redi at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/103626] _GLIBCXX_HOSTED should respect -ffreestanding Date: Sun, 18 Sep 2022 06:41:13 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: libstdc++ X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: redi at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D103626 --- Comment #5 from Jonathan Wakely --- If a header doesn't depend on any of , etc and could work for freestanding, do we want to explicitly disable out with #error, or make it available as an extension? Since the direction in the standard is to enable anything that can work freestanding, we could be liberal in freestanding extensions. That was my thinking anyway.=