From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Joe Ramsay <Joe.Ramsay@arm.com>, <libc-alpha@sourceware.org>
Subject: Re: [PATCH v5 2/2] Enable libmvec support for AArch64
Date: Wed, 3 May 2023 11:36:53 +0100 [thread overview]
Message-ID: <ZFI5RZZJDC5pehro@arm.com> (raw)
In-Reply-To: <20230412133749.40588-1-Joe.Ramsay@arm.com>
The 04/12/2023 14:37, Joe Ramsay via Libc-alpha wrote:
> This patch enables libmvec on AArch64. The proposed change is mainly
> implementing build infrastructure to add the new routines to ABI,
> tests and benchmarks. I have demonstrated how this all fits together
> by adding implementations for vector cos, in both single and double
> precision, targeting both Advanced SIMD and SVE.
>
> The implementations of the routines themselves are just loops over the
> scalar routine from libm for now, as we are more concerned with
> getting the plumbing right at this point. We plan to contribute vector
> routines from the Arm Optimized Routines repo that are compliant with
> requirements described in the libmvec wiki.
>
> Building libmvec requires minimum GCC 10 for SVE ACLE. To avoid raising
> the minimum GCC by such a big jump, we allow users to disable libmvec
> if their compiler is too old.
>
> Note that at this point users have to manually call the vector math
> functions. This seems to be acceptable to some downstream users.
Reviewed-by: Szabolcs Nagy <szabolcs.nagy@arm.com>
i'll rebase the news entry and commit this.
thanks.
next prev parent reply other threads:[~2023-05-03 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 13:37 Joe Ramsay
2023-05-03 10:36 ` Szabolcs Nagy [this message]
2023-05-03 16:50 ` Joseph Myers
2023-05-04 9:41 ` [COMMITTED] aarch64: fix SVE ACLE check for bootstrap glibc builds Szabolcs Nagy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZFI5RZZJDC5pehro@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=Joe.Ramsay@arm.com \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).