From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id BDF7A3858CDB; Thu, 20 Jul 2023 09:58:23 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BDF7A3858CDB DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1689847103; bh=8vVdJsTcWGIdgYeQM/YwJNR3VXSlEpcYDkEEf3gy5+I=; h=From:To:Subject:Date:In-Reply-To:References:From; b=c56hiQBgGvp0C8wzL9+Jt4C027AgOzigJg6mu4faz9m9sXGkwg0dsZ94CUuICJ+Ua 80gqjhfLSopxIPtKTrIYCAuv1vchTtDxNjXJwLqXvNOFD2ttS5DJdGB0Fq/StsUEZd fu68DfKz0BjSmTm5Myxsnsa46ye5Ydv967IkW2GM= From: "kito at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/110751] RISC-V: Suport undefined value that allows VSETVL PASS use TA/MA Date: Thu, 20 Jul 2023 09:58:23 +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: X-Bugzilla-Severity: normal X-Bugzilla-Who: kito at gcc dot gnu.org 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=3D110751 --- Comment #4 from Kito Cheng --- > OK, so TA is either merge or all-ones. Yes, your understand is correct, just few more detail is that can be mixing with either merge or all-ones. e.g. An 4 x i32 vector with mask 1 0 1 0 Op =3D | a | b | c | d | Mask =3D | 1 | 0 | 1 | 0 | the result could be: | a | b | c | d | | a | all-1 | c | d | | a | all-1 | c | all-1 | | a | all-1 | c | d | > Not sure how you can use MA at the moment since you specify an existing o= perand in your target hook. As far as > I can see there's no value the target hook can provide that matches any of the implementation semantics? That's the key point - we don't know how to return an undefined value there= , we have intrinsic can generate undefined value, but it seems impossible to generate that within the hook.=