From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D312A3858D1E; Mon, 3 Oct 2022 20:50:53 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D312A3858D1E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1664830253; bh=XFxWiAyGoSznBRG9iMoSI2aIirt9UoVxFfBhqh69o74=; h=From:To:Subject:Date:In-Reply-To:References:From; b=is3gctAUR4p7qmKpNhkEXJ14vl1eKoGLqJ8Ep/XuqLsSscnpuZ/3eY6I3y1oTxYpQ LvjcYiNSj/vkP7zLAnlbyPDuEM1r9NpXxmXq0YMtQgMoLLlYre1DA3MP2YPRAtphCa kU99RtuxBlOxDLeEXDSsrBpRWdJjt2QpWfiLmsW4= From: "unlvsur at live dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/107135] array::at() method should not be in for freestanding C++ Date: Mon, 03 Oct 2022 20:50:53 +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: 13.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: unlvsur at live dot com X-Bugzilla-Status: UNCONFIRMED 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=3D107135 --- Comment #7 from cqwrteur --- (In reply to cqwrteur from comment #6) > Comment on attachment 53663 [details] > Define function for freestanding >=20 > std::terminate() or std::abort() or __builtin_trap()?? >=20 > std::terminate() has the issue of set_terminate() which causes trouble. >=20 > GCC optimizes __builtin_trap() best but it is not standard. >=20 > What about __builtin_abort()??? maybe we could just mark std::terminate as weak?=