From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: newlib@sourceware.org, Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
Cc: Kinsey Moore <kinsey.moore@oarcorp.com>
Subject: Re: Integration of new patches from ARM's optimized-routines repo
Date: Thu, 8 Sep 2022 09:13:07 +0200 [thread overview]
Message-ID: <15d56c4c-6b4d-5a82-3287-60bbc894e4f5@embedded-brains.de> (raw)
In-Reply-To: <1f4ee7ef-176d-4880-c772-ea540b273adf@oarcorp.com>
Hello Richard,
On 22/04/2022 15:35, Kinsey Moore wrote:
> Hi,
>
> A while back, we had a conversation about getting AArch64 ILP32 support
> added to the hand-coded assembly to fully support the ILP32 ABI under
> newlib. It was suggested that I get that patch into the upstream
> optimized-routines repository and that it be pulled in from that source
> once available.
>
> The patch I submitted there was accepted quite a while back and I was
> wondering how often that repository gets pulled into newlib for updates.
> Is there something else I can do to assist with this update?
is there someone from ARM who takes care that the files imported from
https://github.com/ARM-software/optimized-routines
in Newlib stay up to date? At the moment it seems that nobody feels to
be responsible to do an update.
Kind regards,
Sebastian
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.huber@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax: +49-89-18 94 741 - 08
Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
prev parent reply other threads:[~2022-09-08 7:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-22 13:35 Kinsey Moore
2022-09-08 7:13 ` Sebastian Huber [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=15d56c4c-6b4d-5a82-3287-60bbc894e4f5@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=Richard.Earnshaw@foss.arm.com \
--cc=kinsey.moore@oarcorp.com \
--cc=newlib@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).