From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BE8B93858035; Thu, 7 Sep 2023 09:32:30 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BE8B93858035 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1694079150; bh=XA/iN1AE9ygeGHTnb1R4n2772IVlQxGN3f9CNG1Dz8w=; h=From:To:Subject:Date:In-Reply-To:References:From; b=lIpfHKLTCINlyqL5OIZ36cEha5mpU5zM6nuPkruAlgG1xNGhN4z/F9QrtoF06SL95 RtZBtdQKpV7UAUhDuLsA0XrGLCcoq8ycx2bdB8NoKyn27PT4dbKJtSNz+R8Cs+eiEa lKeZW0n1+q5kgwYGwBTrCQNb0Vlt87f/V6RuV+Eg= From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug go/111310] BITINT_TYPE unsupported in godump.cc Date: Thu, 07 Sep 2023 09:32:29 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: go X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: ian at airs dot com 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=3D111310 --- Comment #3 from Jakub Jelinek --- Note, there is no guarantee that _BitInt(32) or _BitInt(64) are passed/returned/laid out exactly like int32_t or int64_t (ditto for 8 and 16 bits), but on the current single target which supports them it is so far the case. _BitInt(128) has different alignment from __int128 though.=