From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 1D32C3858D32; Wed, 12 Apr 2023 06:19:15 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 1D32C3858D32 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1681280355; bh=2xqr5ufHiPwROLRDP6tRM43nBNvJA3YPe2dZuO1AIZs=; h=From:To:Subject:Date:In-Reply-To:References:From; b=A8quLInDHRi9Oi3buEENBUiiTmaG/w5vhyP1zei4YKnXl5P4TZ8h9PlqdyNz2NnQ7 r1BEo3BnUJmK+tBPOf+HqVZ3SG6XUFm9HrMK8kYdX299cfoxBsOEhzWT5gwl6tLZGt GLrGAQU/zfynLcdkX0xdNXDHMHvnUpMLWTxiwH3c= From: "kito at gcc dot gnu.org" 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:19:14 +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: kito 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: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: everconfirmed bug_status cf_reconfirmed_on 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 Kito Cheng changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Last reconfirmed| |2023-04-12 --- Comment #3 from Kito Cheng --- Title might little bit misleading, -march=3Drv64gc_zve32x_zvl64b is valid a= rch configuration, invalid thing is vint64m*_t and vuint64m*_t are invalid for rv64gc_zve32x.=