From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 8C180385842B; Mon, 26 Feb 2024 11:24:56 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 8C180385842B DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1708946696; bh=hvDo8E/eyjZMDRSb98Ddpvnfhc+22QYvlt+ZxyfK1Og=; h=From:To:Subject:Date:In-Reply-To:References:From; b=vNZqazRjFIh6h2GUxvGh2ujJXTu/aAXqYuxeEa1O4fZXR4HNxTP9tk5/sl0ZQBnPZ 01hh6uEs+eBz+tvO7DN2Z4Gr5WJGI8EEAXRnPUyNgxb8EfdgX4sRfu9IKLiyvRIEiT WUYBe0R3vJLAQn1t9XNbaeTfjApxmbTn1c4kb8PY= From: "juzhe.zhong at rivai dot ai" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/114109] x264 satd vectorization vs LLVM Date: Mon, 26 Feb 2024 11:24:55 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: middle-end X-Bugzilla-Version: 14.0 X-Bugzilla-Keywords: missed-optimization X-Bugzilla-Severity: enhancement X-Bugzilla-Who: juzhe.zhong at rivai dot ai X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- 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=3D114109 --- Comment #3 from JuzheZhong --- (In reply to Robin Dapp from comment #2) > It is vectorized with a higher zvl, e.g. zvl512b, refer > https://godbolt.org/z/vbfjYn5Kd. OK. I see. But Clang generates many slide instruction which are expensive in real hardware. And also vluxei64 is also expensive. I am not sure which is better. It should be tested on real RISC-V hardware = to evaluate their performance rather than simply tested on SPIKE/QEMU dynamic instructions count.=