From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 7E7313858D28; Fri, 27 Jan 2023 22:56:39 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 7E7313858D28 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1674860199; bh=6Dkl1MCvrM7YbNW1PSeA7EiJAiAzpHWw1B91+1GuDJY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ZSauT0atDQOVNn7ZEiH2LL8xEi40kWuk8x9Pg1PnzII1/kbdHhj51+HI17iULrZtC a/2e5pTINYYTYumNWN+C4nQMP4pql2jD26U7W6x9LsDoJxrzot27tbhXhOb90xkLr3 pt+YEfPM2a8C8RrGz9aQqILKqcqM7hfXX9DGxrOc= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/108574] [13 Regression] wrong code at -Os and above on x86_64-linux-gnu Date: Fri, 27 Jan 2023 22:56:39 +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: unknown 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: 13.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: everconfirmed short_desc target_milestone keywords cf_reconfirmed_on bug_status 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=3D108574 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Summary|wrong code at -Os and above |[13 Regression] wrong code |on x86_64-linux-gnu |at -Os and above on | |x86_64-linux-gnu Target Milestone|--- |13.0 Keywords| |wrong-code Last reconfirmed| |2023-01-27 Status|UNCONFIRMED |NEW --- Comment #3 from Andrew Pinski --- (In reply to Zhendong Su from comment #0) > It appears to be a recent regression from 12.2. In the testcase from comment #0, pre is messing it up because of an uninitialized variable on one path (which is not taken). Note somehow the statement: d >=3D b; changes the IR slightly ... testcase in comment #1 also depends on an uninitialized variable on a path = not taken too (in that case j). testcase in comment #2 also looks similar and depends on an unintialized variable on a path not taken too.=