From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E299B385841D; Fri, 16 Jun 2023 22:23:10 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E299B385841D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1686954190; bh=RczvRNsq0q38vDMhap/SdY7q18RbwVk0JnGdIx8Q/5E=; h=From:To:Subject:Date:In-Reply-To:References:From; b=hfpd1d5TSCFyDFg/1Cvs0uJ9SPxLTH+HaHmdgOB0OlgPT0HROmXsLTvWiErN3h/5S GHFa6WwwDLqs8l2uE2XmsQ76NDeTyluvPM2KNw8dC+OIiczpiOMDiMvr5CiRrA77wT 6dJT6XxTrDaI0MCM/2qgPUMvFe6usaWKXNLeLG1M= 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: Fri, 16 Jun 2023 22:23:10 +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 #11 from Andrew Pinski --- >From the duplicate bug report analysis: # RANGE [irange] short int [0, 1] NONZERO 0x1 # n_lsm.35_15 =3D PHI <_10(9), n_lsm.35_45(12)> ... # RANGE [irange] short int [0, 1] NONZERO 0x1 # n_lsm.35_45 =3D PHI # RANGE [irange] short int [0, 1] NONZERO 0x1 _10 =3D (short intD.17) _9; But the range of _69(D) is really undefined .... There is nothing phiopt/match is doing incorrectly due to the above, rather= it is ranger that might be considering the wrong/incorrect information for uninitialized variables ...=