From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id AA8A8385E012; Fri, 27 Mar 2020 07:07:08 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org AA8A8385E012 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1585292828; bh=P1vkboNhUn4wKa5NcUqdnGV+77kKpr4248bVSdS7NHI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=VKVmPPotY5Qni3iJwszJgoC7/o1nNY6vOcq4rD0YDSW/DbK/XrfGtwfIERHwM0Mgp xbxa9aXf8JL3a/C9HVYiMc0Scl9XJVmEpdnFZELs4y6f3CDC3BO2Kj0O6yjH3eEehh vobpKciqx4LKE6GLY9/E5EPyY/DkST8WW9ElOht0= From: "jbeulich at suse dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/94343] [10 Regression] invalid AVX512VL vpternlogd instruction emitted for -march=knl Date: Fri, 27 Mar 2020 07:07:08 +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: 10.0 X-Bugzilla-Keywords: missed-optimization, wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: jbeulich at suse dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org X-Bugzilla-Target-Milestone: 10.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: 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 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Mar 2020 07:07:08 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D94343 --- Comment #12 from jbeulich at suse dot com --- (In reply to Jakub Jelinek from comment #8) > Created attachment 48128 [details] > gcc10-pr94343.patch >=20 > Updated patch. A variant to that would be 4 separate patterns I guess, n= ot > sure if that would be shorter. May I suggest that the testcases also check for the 0x55 immediate? The potential of VPTERNLOG allows for much wider use (with different immediates= ) in principle, so the correct choice of immediate would imo better be validated here as well.=