From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 351573858D33; Mon, 26 Jun 2023 16:07:04 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 351573858D33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1687795624; bh=tym82/08v+L3JF/OTdLkEuwyxbnIMJ8AkNqfdHQxvXA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=aUkGDdc0rFxwso7IN3f+9XvBhE/k2JcKJf3zh4RldgRGtJDfYrfuH2uWSjKdfKbQF hbKudnFz6lGa/RW/jULTlydXqO/QgQQj1VlqA7dNiGSqg+t4308+CJ7yz70zVbIXnD 4GOSwWLOb0X5tho4iztvX+vgcTXUoLKzPKjqVqN0= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/110410] [14 Regression] Different results between -O0 and -O2 Date: Mon, 26 Jun 2023 16:07:04 +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: 14.0 X-Bugzilla-Keywords: missed-optimization, 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: dependson bug_status keywords everconfirmed cf_reconfirmed_on 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=3D110410 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Depends on| |110252 Status|UNCONFIRMED |NEW Keywords|needs-bisection |missed-optimization Ever confirmed|0 |1 Last reconfirmed| |2023-06-26 --- Comment #5 from Andrew Pinski --- This is basically a dup of bug 110252 as the range of iftmp.7_27 is flow sensitive here. BUT there is a missed optimization before hand though: # RANGE [irange] unsigned int [0, 0] NONZERO 0x0 iftmp.7_27 =3D (unsigned intD.9) _7; This shows up in dom3. So keeping it open for that case too ... Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D110252 [Bug 110252] [14 Regression] Wrong code at -O2/3/s on x86_64-linux-gnu=