From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 7C965385842E; Wed, 2 Nov 2022 16:30:47 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7C965385842E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1667406652; bh=XNDVEqhIUbL2O6UqAcCZ3IB1MMYMB7KxYdbGEERRrxs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=QZaJhPgnI5MV0KLJhF7CH2YM4YcACKCxiyO+Y0xzn1kkGnPphvHmuJ76itQwej3lA YLkyoys2Yysjr6owD9RW9qN5TRtVrVrZ2aunQSjDkTVGe0YP3Tz9RdzQMWW0UqsJU8 5p4XyRRbH+yzqGYYYm41AqInRUVB0LIUVotfrKBU= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/105532] [11/12/13 Regression] UBSAN: gcc/hwint.h:293:61: runtime error: shift exponent 64 is too large for 64-bit type 'long unsigned int' Date: Wed, 02 Nov 2022 16:30:46 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: tree-optimization X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: ice-on-valid-code X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: pinskia at gcc dot gnu.org X-Bugzilla-Target-Milestone: 11.4 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=3D105532 --- Comment #5 from Andrew Pinski --- (In reply to Andrew Pinski from comment #2) > Confirmed. > The bug is either in tree_nonzero_bits and should not be doing: > return wi::shwi (-1, TYPE_PRECISION (TREE_TYPE (t))); Just FYI, TYPE_PRECISION for vectors is a log2 of the number of elements, s= ee TYPE_VECTOR_SUBPARTS. Which is why you get 0 here since we have 1 element.=