From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 0B50A3851AB8; Thu, 17 Aug 2023 18:39:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 0B50A3851AB8 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1692297585; bh=jvYHZMHnkMEOsQ8RoMem0AslJpCeVj4m8dApTqaZSrY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=QGIwSbZB7iS1NYyIA55Fb7FdXQYTlBwEvyDPKGWrk+vjmFvVzAaEcCIwFD/gTHL4a BNCu3dXP3PkxqEsOrY7GYsezB3JIEG2iCo4xaJPLyTRCLsF7F7clJ4EmQYo8ip/tWt dMBo5eYd4xRKM863yXERiIzPLAZrsFuF6IUkCGAg= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/111048] [14 Regression] Wrong AVX2 code on highway-1.0.6 on -O2 and above Date: Thu, 17 Aug 2023 18:39:44 +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: 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: bug_status everconfirmed component 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=3D111048 Andrew Pinski changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever confirmed|0 |1 Component|middle-end |tree-optimization Last reconfirmed| |2023-08-17 --- Comment #2 from Andrew Pinski --- Setting value number of vect__4.12_36 to { 255, 63, 15, 3, 255, 63, 15, 3, = 255, 63, 15, 3, 255, 63, 15, 3 } (changed) Match-and-simplified VEC_PERM_EXPR <{ 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0= , 0, 0, 0 }, vect__4.12_36, { 0, 16, 1, 17, 2, 18, 3, 19, 4, 20, 5, 21, 6, 22, 7= , 23 }> to { 0, 255, 0, 63, 0, 15, 0, 3, 0, 255, 0, 63, 0, 239, 0, 123 } Confirmed that is definitely wrong. I don't even know where 239 and 123 came from ...=