From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id B65683856961; Tue, 13 Jun 2023 11:41:52 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B65683856961
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1686656512;
	bh=hShBCv2JbyYPEL3q/u78wfl3EhogomD/d2IzpCHf8mg=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=iH2uXJuhMOpEVpZ8EPoTwfOT8T0gcFNUdqDhCTPVByDE+Gpx7VPq5SwbohpuZjMv6
	 LNbZkySCvWsLBoVqlAvCtKHSOMMQH4irMPYvO0FKva+6a+CUTq3TxDH8a/3SIa3/cm
	 /eBuNg+RTieP8doL74QEXFLH/TatRWA6C4NnILEg=
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/110227] [13/14 Regression] gcc generates invalid AVX-512
 code
Date: Tue, 13 Jun 2023 11:41:51 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 13.1.0
X-Bugzilla-Keywords: assemble-failure
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub 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.2
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-110227-4-R8W1njz6UQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-110227-4@http.gcc.gnu.org/bugzilla/>
References: <bug-110227-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D110227

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Looking at that commit, it also introduced weird formatting:
          return "vpcmpeqd \t %t0, %t0, %t0";
and
          return "vpcmpeqd \t %x0, %x0, %x0";
and
      return "vpcmpeqd \t %x0, %x0, %x0";
definitely shouldn't have the spaces around \t on either side.
But sure, agree the alternative with BH constraint on source should use x
rather than
v constraint on destination.=