From: Kinsey Moore <kinsey.moore@oarcorp.com>
To: Kinsey Moore <kinsey.moore@oarcorp.com>,
"joel@rtems.org" <joel@rtems.org>,
Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: Newlib <newlib@sourceware.org>
Subject: RE: End of year snapshot
Date: Thu, 17 Dec 2020 15:44:30 +0000 [thread overview]
Message-ID: <MN2PR19MB37274687BC19EBA9AF56130290C40@MN2PR19MB3727.namprd19.prod.outlook.com> (raw)
In-Reply-To: <MN2PR19MB372706F9024A8D3E985A8F0B90C70@MN2PR19MB3727.namprd19.prod.outlook.com>
-----Original Message-----
From: Newlib <newlib-bounces@sourceware.org> On Behalf Of Kinsey Moore
Sent: Monday, December 14, 2020 08:48
To: joel@rtems.org; Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: Newlib <newlib@sourceware.org>
Subject: RE: End of year snapshot
> From: Joel Sherrill <joel@rtems.org>
> Sent: Saturday, December 12, 2020 10:25
> To: Sebastian Huber <sebastian.huber@embedded-brains.de>
> Cc: Jeff Johnston <jjohnstn@redhat.com>; Newlib <newlib@sourceware.org>; Kinsey Moore <kinsey.moore@oarcorp.com>
> Subject: Re: End of year snapshot
>>
>> And I think Kinsey got fixes in to that code for the ilp32 aarch64 multilib.
>>
>> A merge from there would be appreciated.
>
> The code to fix ILP32 in optimized-routines is up for review at the moment. I expect it will be merged today or tomorrow.
This change has now been merged into the upstream optimized-routines repository in a slightly different form than was posted here. If one of the ARM maintainers could pull that in, that would be great.
Kinsey
prev parent reply other threads:[~2020-12-17 15:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-11 21:41 Jeff Johnston
2020-12-12 12:30 ` Sebastian Huber
2020-12-12 16:25 ` Joel Sherrill
2020-12-14 14:47 ` Kinsey Moore
2020-12-17 15:44 ` Kinsey Moore [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=MN2PR19MB37274687BC19EBA9AF56130290C40@MN2PR19MB3727.namprd19.prod.outlook.com \
--to=kinsey.moore@oarcorp.com \
--cc=joel@rtems.org \
--cc=newlib@sourceware.org \
--cc=sebastian.huber@embedded-brains.de \
/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).