From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 6BBA8385AC19; Wed, 24 Aug 2022 06:51:35 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6BBA8385AC19 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1661323895; bh=JShHGj+N/2Ni3WZyO1d6+/Mh1Is70JhSzMTkSvUGlZk=; h=From:To:Subject:Date:In-Reply-To:References:From; b=PNsC2graf+Is0auaHz3PVgrBOadJPboTjjJia4KaHqURd9BW2lNDeb3a30Hlx0LgE 89JBB9Kd4ZIJvA/r9Zb0ViRCLKiqx24Bn/yOhraL4QxtIJGlYO1Fk8vKbOuFxiXbJb +nH3z4GZxbxPYFwHCslFmD7oFRw5f0wbEWoFLd+M= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/106322] [12 Regression] tree-vectorize: Wrong code at O2 level (-fno-tree-vectorize is working) since r12-2404-ga1d27560770818c5 Date: Wed, 24 Aug 2022 06:51:34 +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: 12.1.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth at gcc dot gnu.org X-Bugzilla-Status: RESOLVED X-Bugzilla-Resolution: FIXED X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: linkw at gcc dot gnu.org X-Bugzilla-Target-Milestone: 12.3 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: resolution cf_known_to_work bug_status cf_known_to_fail 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=3D106322 Richard Biener changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Known to work| |12.2.1 Status|ASSIGNED |RESOLVED Known to fail| |12.2.0 --- Comment #50 from Richard Biener --- (In reply to Kewen Lin from comment #49) > Hi Richi, >=20 > One thing I'm not sure about is that if we want to backport this to gcc-11 > and gcc-10? Although the failure got exposed by .MULH pattern recog which= is > only in gcc-12, IMHO the underlying issue exists in gcc-10 and gcc-11. It's enough to backport to 12.=