Re: Minimum compiler version?

Tomas Mraz <[email protected]> Thu, 10 Jul 2025 11:13:10 +0200
Newsgroups gmane.comp.encryption.openssl.user
Message-ID <[email protected]>
perlasm is definitely not an overkill for CPUs that are used on
multiple platforms such as Windows.

If you're targetting RISC-V CPU which means AFAIK only POSIX platforms
with fairly new versions of gcc and/or clang, then this might be
acceptable in form of C intrinsics. However please note there is
already a lot of RISC-V assembler written in perlasm so doing it in
perlasm would still be preferred.

Tomas Mraz, Public Support and Security Manager, OpenSSL Foundation

On Wed, 2025-07-09 at 22:29 -0700, Eric Roshan-Eisner wrote:
> Thanks for the replies; that makes sense. I'll fix up my code and
> send a PR with a new asm file. Perlasm seems like overkill.
> 
> On Wednesday, July 9, 2025 at 2:20:49 PM UTC-7 Neil Horman wrote:
> > you'll find our supported platform list here:
> > https://mirror.openssl-library.org/policies/general-supplemental/platforms/
> > 
> > Generally speaking our supported platform use gcc 9 as a minimum,
> > but we don't officially support RISCV (note they are considered
> > unadopted on that list).  For those platforms the compilers that
> > have been used by anyone who has tried are a myriad of older
> > compilers (for instance the hpux targets claim gcc, and the latest
> > version that I know of on that OS is gcc 4), so you may be likely
> > to experience pushback from any implementation that uses the newer
> > intrinsics.
> > 
> > Neil
> > 
> > 
> > On Wed, Jul 9, 2025 at 4:57 PM Eric Roshan-Eisner
> > <[email protected]> wrote:
> > > I'm looking into contributing my RISCV Vector implementation of
> > > poly1305 [1] to openssl. It would need to be rewritten to conform
> > > to openssl's internal asm API. I see that most of the simd
> > > implementations are in perlasm. Could I contribute a RISCV
> > > implementation in C using the newish vector compiler intrinsics
> > > [2]? These are supported by gcc 14 and clang 17. I can't find any
> > > documented minimum compiler versions for the project as a whole,
> > > or for RISCV in particular.
> > > 
> > > Can openssl use features from newer compilers, or otherwise gate
> > > this implementation at build time?
> > > 
> > > -Eric
> > > 
> > > [1] https://github.com/edre/rvv-chacha-poly
> > > [2] https://github.com/riscv-non-isa/rvv-intrinsic-doc
> > 

-- 
Tomáš Mráz, Public Support and Security Manager, OpenSSL Foundation
Join the Code Protectors or support us on Github Sponsors
https://openssl-foundation.org/donate/

-- 
You received this message because you are subscribed to the Google Groups "openssl-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openssl-users+unsubscribe-MCmKBN63+Bmbup2nOX2J7Q@public.gmane.org
To view this discussion visit https://groups.google.com/a/openssl.org/d/msgid/openssl-users/48a4c4838f4e6eb4d9f28ceeeb911c3611a7c865.camel%40openssl.org.