From: Kinsey Moore <kinsey.moore@oarcorp.com>
To: "joel@rtems.org" <joel@rtems.org>,
Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: Jeff Johnston <jjohnstn@redhat.com>, Newlib <newlib@sourceware.org>
Subject: RE: End of year snapshot
Date: Mon, 14 Dec 2020 14:47:36 +0000 [thread overview]
Message-ID: <MN2PR19MB372706F9024A8D3E985A8F0B90C70@MN2PR19MB3727.namprd19.prod.outlook.com> (raw)
In-Reply-To: <CAF9ehCUjOzL=WxYEgbDBkE8ydw4sjD4_ZW2WyqnzuXaUSjBeeg@mail.gmail.com>
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
On Sat, Dec 12, 2020, 6:30 AM Sebastian Huber <sebastian.huber@embedded-brains.de<mailto:sebastian.huber@embedded-brains.de>> wrote:
Hello Jeff,
On 11/12/2020 22:41, Jeff Johnston via Newlib wrote:
> If there are any changes that you wish to be part of the year-end snapshot
> that haven't been reviewed/posted yet, please notify the list.
it would be nice to include this fix:
https://sourceware.org/pipermail/newlib/2020/018170.html
There are probably better long term solutions, for example
synchronization of Newlib with
https://github.com/ARM-software/optimized-routines
but this small patch fixes an otherwise broken Newlib for Armv8-R.
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.
Kinsey
next prev parent reply other threads:[~2020-12-14 14:47 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 [this message]
2020-12-17 15:44 ` Kinsey Moore
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=MN2PR19MB372706F9024A8D3E985A8F0B90C70@MN2PR19MB3727.namprd19.prod.outlook.com \
--to=kinsey.moore@oarcorp.com \
--cc=jjohnstn@redhat.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).