Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   =?ISO-8859-1?Q?R=E9mi?= Denis-Courmont <remi@remlab.net>
To:     linux-riscv@lists.infradead.org
Cc:     linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 05/12] RISC-V: crypto: update perl include with helpers for
 vector (crypto) instructions
Date:   Tue, 11 Jul 2023 21:04:57 +0300
Message-ID: <10238181.0Rfz7avHUX@basile.remlab.net>
Organization: Remlab
In-Reply-To: <20230711153743.1970625-6-heiko@sntech.de>
References: <20230711153743.1970625-1-heiko@sntech.de>
 <20230711153743.1970625-6-heiko@sntech.de>
MIME-Version: 1.0
Content-Transfer-Encoding: 8BIT
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

Le tiistaina 11. heinäkuuta 2023, 18.37.36 EEST Heiko Stuebner a écrit :
> From: Heiko Stuebner <heiko.stuebner@vrull.eu>
> 
> The openSSL scripts use a number of helpers for handling vector
> instructions and instructions from the vector-crypto-extensions.

Uh but the kernel RVV code requires an assembler that supports the `.option 
arch` directive and the V extension anyway.

Is there a need to wrap vector load/store and ALU instructions from the Vector 
spec? This trick should only be necessary for the Zvk*-specific stuff, AFAICT.

(Also FWIW, this can be done directly with .macro inside a header file, without 
involving Perl.)

-- 
Rémi Denis-Courmont
http://www.remlab.net/