From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 64C483858D3C; Mon, 20 May 2024 05:50:17 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 64C483858D3C DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1716184217; bh=V7lR8Iby1q/TtsQ7TNRFwjDVaUlq7SifA3zirVrKp20=; h=From:To:Subject:Date:In-Reply-To:References:From; b=bCbNyNg4ipW/n5kgNfTxctYsmAM4JBzBp3dmh+Wjkz09lqQ04n0GFxxNRf9y/stMz tmB7UPQUolQcf8Jq7vSQq0F3XLGf1/3gLR/VY7xUge4nwnC/JO7IW2KujcBPhsoQQQ a4qYPJvBSoQ7TXho+Hhs9D+XH18680DD5Nr+MHzI= From: "haochen.jiang at intel dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/115069] [14/15 regression] 8 bit integer vector performance regression, x86, between gcc-14 and gcc-13 using avx2 target clones on skylake platform Date: Mon, 20 May 2024 05:50:16 +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: 14.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: normal X-Bugzilla-Who: haochen.jiang at intel dot com 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.2 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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D115069 --- Comment #12 from Haochen Jiang --- (In reply to Hongtao Liu from comment #11) > (In reply to Haochen Jiang from comment #10) > > A patch like Comment 8 could definitely solve the problem. But I need to > > test more benchmarks to see if there is surprise. > >=20 > > But, yes, as Uros said in Comment 9, maybe there is a chance we could d= o it > > better. >=20 > Could you add "arch=3Dskylake-avx512" to target_clones and try disable wh= ole > ix86_expand_vecop_qihi2 to see if there's any performance improvement? > For x86, cross-lane permutation(truncation) is not very efficient(3-4 cyc= les > for both vpermq and vpmovwb). When I disable/enable ix86_expand_vecop_qihi2 with arch=3Dskylake-avx512 on trunk, there is no performance regression comparing to GCC13 + avx2. It seems that the regression only happens when GCC14 + avx2.=