From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 9896F3856DCD; Tue, 25 Oct 2022 21:50:25 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9896F3856DCD DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1666734625; bh=ZH93z5k81Xi1ZLKBNEH4tX8bUehCKwi+xv1wmm14tlQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=fHlqSF31+3E8pMHF59QE02YkgM//qDjAJY/ReMd6Jy64RnYLs/mJ8JgFAsiLDF5xZ gNLzuJjDDZQVAiIAM7kDgzErMNweVJODz10Li3fbOq6Av6ZSUTTIuJ76dhKN6yuCD8 Gjclft4xJ7vWvhsLk4sgLUHl4Sxvt9YdvEF76BMk= From: "segher at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/102989] Implement C2x's n2763 (_BitInt) Date: Tue, 25 Oct 2022 21:50:25 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c X-Bugzilla-Version: 12.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: segher 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=3D102989 --- Comment #21 from Segher Boessenkool --- (In reply to Jakub Jelinek from comment #19) > (In reply to Segher Boessenkool from comment #16) > > (In reply to Jakub Jelinek from comment #15) > > > PowerPC I think does, not sure about s390. > >=20 > > Does what? >=20 > Published psABI which ought to specify how to pass/return _BitInt(N) and > unsigned _BitInt(N). psABI is an x86 thing? But there are various ABIs for PowerPC that have public documentation, six or so, and GCC has support for most of those. None of them are "processor specific" (most are OS specific, instead), and they differ in very fundamental things, in places. They are much related as well of course, either because there is an obvious choice, or history. Many of those ABIs have not seen updates for decades, and are unlikely to anymore. OTOH the GCC support for them has been updated over time, there often is only one sane choice anyway. We'll make decisions on what ELFv2 will do for _Bitint when it is closer in time than it is now. The only interesting choice is whether values in memory have undefined bits -- and they likely should, simply because all other padding bits are undefined as well.=