From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 192E53861869; Fri, 1 Dec 2023 21:53:47 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 192E53861869 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1701467627; bh=gZ4MxECR9W/EZ56+/Up8PtV5hr3YdjpfMXFoNmqdygA=; h=From:To:Subject:Date:In-Reply-To:References:From; b=PPv99wLIJu/Jr01pwSY5NLKlkM84qiLrnSwUURGuMfRXOP4XhycP7WBBseKvXOe/M qS32AaBD4Z/Hid7LcfhWiRGRbus2q+y9DqdS6dBlMX/HRUaus/gDIPGcHKjZV4evC/ +T0K1/s93cpb+YJeuVtComFMYQQimSDvIQD0NKKE= From: "pinskia at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/112817] RISC-V: RVV: provide a preprocessor macro for VLS codegen Date: Fri, 01 Dec 2023 21:53:46 +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: enhancement X-Bugzilla-Who: pinskia 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=3D112817 --- Comment #1 from Andrew Pinski --- >gcc doesn't, which is a bit of pain for downstream projects such as xsimd. Does it even make sense to define this? Projects like xsimd seems to be good for fixed length SIMD but it seems to have a broken idea for non-fixed leng= th SIMD like SVE and RVV. Would it better to have xsimd provide better interfa= ces instead for non-fixed length vectors and not provide a fixed length API at = all?=