From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 00ABA3858CDB; Fri, 1 Dec 2023 11:46:35 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 00ABA3858CDB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1701431196; bh=Z94o1adIb6zTTtf5i+GCqgQX9J02eXrUc0JyTyYeW+A=; h=From:To:Subject:Date:In-Reply-To:References:From; b=RFNiJWfDwxrKdHevwb//WEg+VgJEbSG8dCItg6ji1hdstIOKlB98lZViiSfYhlaBU swBxBBDKViKEnZy2GqS48OEjAnt/bEfOOqQ5c3FUyYYEEACZdTqEpDvecWeM8nbfC1 pYouE9p4xJTe61IlbLSSd+4261HA88mxuJYQOb0E= From: "rguenth at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/112740] [14 Regression] wrong code with vector compare on riscv64 at -O0 Date: Fri, 01 Dec 2023 11:46:33 +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: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: rguenth 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: 14.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 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D112740 --- Comment #11 from Richard Biener --- The only thing that's maybe suspicious is that machine_mode mode =3D GET_MODE (target); but we test /* Use sign-extension for uniform boolean vectors with integer modes. Effectively "vec_duplicate" for bitmasks. */ if (!TREE_SIDE_EFFECTS (exp) && VECTOR_BOOLEAN_TYPE_P (type) && SCALAR_INT_MODE_P (mode) where we might want to test SCALAR_INT_MODE_P (TYPE_MODE (type)) instead. Not sure if we ever call store_constructor with target not having the same mode as 'exp' though ... Or we should check that mode =3D=3D TYPE_MODE (ty= pe) since we're moving to target anyway.=