From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id C8E163858D28; Wed, 12 Apr 2023 06:08:03 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C8E163858D28 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1681279683; bh=zuNWglspgECi8IiQlRnBnxLKRIKpM17WRWaOar4ILZ8=; h=From:To:Subject:Date:In-Reply-To:References:From; b=N+kCKRjoNXxPvfLXmhEaQzV1VzV3s96DbkixXbMWZ+cVuE3obmXqVxNNiDBESCfJ6 UD0dVgVq89OPSKTMGc0gKctPyj0ePcBXTb60OFzKX5kzpP6dKwHAWh06namxogfUbH +HMYhH0dsMAbVajJCmlj9DIioHZe/SRJV5E/K2E8= From: "pan2.li at intel dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/109479] [RISC-V] Build with rv64gc_zve32x_zvl64b should fail but actually not Date: Wed, 12 Apr 2023 06:08:03 +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: X-Bugzilla-Severity: normal X-Bugzilla-Who: pan2.li at intel dot com 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=3D109479 --- Comment #2 from Li Pan --- Thanks for reminding me. Sorry for missing that and will pay more attention= to this next time. The test case. #include "riscv_vector.h" vint64m1_t foo () { vint64m1_t v; return v; } According to the RVV SPEC below, the 'vint64m1_t' (aka '__rvv_int64m1_t') requires the 'zve64x' extensions. https://github.com/riscv/riscv-v-spec/blob/master/v-spec.adoc#18-standard-v= ector-extensions=