From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B20633858D39; Sat, 17 Jun 2023 17:52:50 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B20633858D39 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1687024370; bh=mDmjt1lCK2h/k4QXrD5iqHaSKatnmOztlSbZAkPcrzE=; h=From:To:Subject:Date:In-Reply-To:References:From; b=oepcYxZW3+besBjAGp8gfgrPfoamkAEuIO1wWEcaGKtmDRziSk9OkIX1cRmz2sPcl jzd/NvN3jZF/eVWGp5EIzIAqCOPmyzMPYbmPerTdlWdKmHFYL7Tlh9MTSK3hUhWhdf hHu909WtLwNYuCNsmOErjlIk0HmDqYlz3i3PqVlY= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/110228] [14 Regression] llvm-16 miscompiled due to an maybe uninitialized and optimizations saying that the uninitialized has a nonzero bits of 1. Date: Sat, 17 Jun 2023 17:52:49 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: pinskia 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: 14.0 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=3D110228 --- Comment #12 from Andrew Pinski --- I should note my reduced testcase does not even need the ranger to tell me = that the range is [0,1] because it uses a bool which has a PRECISION of 1. If an expand solution is not implemented in a few months, I will submit a p= atch which disables the `bit_ior` case and leave a comment there on referencing = PR 71762 and this bug.=