From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E1C3E3858C27; Wed, 24 May 2023 14:57:15 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E1C3E3858C27 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1684940235; bh=U8Jky5fGWvIM7jUAldc8xfN7jMf0nFB25jGc6WKc8dQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=UbaSFcuCmN6xrx9m2KfmpfS56bjNN5pUcsyLg+mJxON0JAiDEMmBKrHm+2QHrTJ90 cruHFsikZSDfGqxIUj4RMJLScADYGvyndqKrx96Y8quPrnQDAxSslJYd9D22Rkxd72 sglLGVu/g5HCeJ8tx7TtRYN7+eSP9Oy/Z4JbrZYg= From: "rguenther at suse dot de" To: gcc-bugs@gcc.gnu.org Subject: [Bug c/102989] Implement C2x's n2763 (_BitInt) Date: Wed, 24 May 2023 14:57:15 +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: rguenther at suse dot de 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 #48 from rguenther at suse dot de --- > Am 24.05.2023 um 16:18 schrieb jakub at gcc dot gnu.org : >=20 > =EF=BB=BFhttps://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D102989 >=20 > --- Comment #47 from Jakub Jelinek --- > But then the pass effectively has to do lifetime analysis of the _BitInt(= N) for > N > 128 etc. SSA_NAMEs and perform the partitioning of those SSA_NAMEs in= to > VAR_DECLs/PARM_DECLs/RESULT_DECLs, so that we don't blow away the local s= tack; > perhaps as you wrote with some local subgraphs turned into a loop which w= ill > handle multiple operations together instead of just one operation per loo= p. > Or just use different VAR_DECLs but stick in clobbers where they will be = dead > and hope out of ssa can merge those. > Anyway, more work than I hoped. > Though, perhaps it can be also done incrementally, with bare minimum firs= t and > improvements later. Sure, this is just what I think users will expect. We don=E2=80=99t have t= he high level infrastructure to do this afterwards such as loop fusion and variable contraction (well, in theory graphite can do it but even there we lack actu= al transform bits).=