public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Joe Ramsay <Joe.Ramsay@arm.com>
Cc: <libc-alpha@sourceware.org>
Subject: Re: [PATCH v2] [RFC] Proposal for implementing AArch64 port of libmvec
Date: Mon, 20 Feb 2023 16:10:17 +0000	[thread overview]
Message-ID: <Y/ObaZq8YJK9m4CN@arm.com> (raw)
In-Reply-To: <20230213164622.23109-1-Joe.Ramsay@arm.com>

The 02/13/2023 16:46, Joe Ramsay via Libc-alpha wrote:
> Any comments/thoughts much appreciated! In particular, the patch
> raises the minimum GCC to 10, in order to be able to submit routines
> written using ACLE instead of assembly. This is clearly a big jump,
> but we have options if this is not acceptable. One option would be to
> submit compiler-generated assembly, similar to the equivalent routines
> under sysdeps/x86_64. If GCC 9 is an acceptable compromise then this
> would only have to be for SVE routines.

1) making the min required gcc version gcc-10 is a big jump, but
probably the cleanest solution.

2) including asm code for old gcc adds complications (e.g. issues
with configuration dependent instrumentation such as pac/bti) for
a rarely tested case.

3) optionally disabling libmvec for old gcc is doable but then the
declarations in math.h should be avoided, so this affects API.

we want users to build with >= gcc-10, but i think this can be
disruptive for some glibc developers (builds running in older
distro environments), so i think 3) may be a reasonable trade-off:
require >= gcc-10 with --enable-mathvec, allow old gcc otherwise.

--disable-mathvec is not expected to be a deployed configuration
that we support in the long term so if we run into issues with it
then we can drop it moving to 1).


      reply	other threads:[~2023-02-20 16:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13 16:46 Joe Ramsay
2023-02-20 16:10 ` Szabolcs Nagy [this message]

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=Y/ObaZq8YJK9m4CN@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).