From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E0C7D385B53D; Tue, 4 Apr 2023 12:54:21 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E0C7D385B53D DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1680612861; bh=nsPP34muQe/SuJm3cR+/vipHZXV+8dQuICJPrIOFXJ8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=nWBUQrDT4oDnLI5zlqzlBOxQ4sWjFj0kGOsGa6i9dLzG/GHV510C8O8sPuP94GP7J bzktZyUsdGTHbJBriWD/aqBEIINvRpDDv7YnEl6v3Jm5oVTutKZ4HzmBdMGrH5GfNC AtQO+MVKdxbiWS9gai7v7HOFz4QnzCeimhGhBwaw= From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109040] [13 Regression] wrong code with v16hi compare & mask on riscv64 at -O2 since r13-4907-g2e886eef7f2b5a Date: Tue, 04 Apr 2023 12:54:20 +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.0 X-Bugzilla-Keywords: wrong-code 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.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc attachments.created 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=3D109040 Jakub Jelinek changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #3 from Jakub Jelinek --- Created attachment 54808 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D54808&action=3Dedit gcc13-riscv-mvconst.patch I think it is weird to have multiple mov like patterns. I've tried to get rid of this by adding a new predicate for *movsi_internal/*movdi_64bit, which after expansion and until end of split1 accepts the splittable constants and turn the current *mvconst_internal int= o a pure splitter. This doesn't fix the PR though, but I think it would be a good idea anyway.=