From: Joel Sherrill <joel@rtems.org>
To: "Alexander Fedotov (OSS)" <alexander.fedotov@oss.nxp.com>
Cc: Sebastian Huber <sebastian.huber@embedded-brains.de>,
Newlib <newlib@sourceware.org>
Subject: Re: How well is the Arm Cortex-R52 supported by Newlib?
Date: Mon, 7 Dec 2020 10:52:39 -0600 [thread overview]
Message-ID: <CAF9ehCVvHjF__UP9j0mpibXHvTNBB9GVwhovR3cu_mxcDvu02Q@mail.gmail.com> (raw)
In-Reply-To: <HE1PR0401MB2363DD47CD534090F5F47A63F4CE0@HE1PR0401MB2363.eurprd04.prod.outlook.com>
On Mon, Dec 7, 2020, 10:31 AM Alexander Fedotov (OSS) via Newlib <
newlib@sourceware.org> wrote:
> Hi Sebastian
>
> I have pushed some changes in libgloss/arm/crt0.S to support
> initialization in Thumb mode. But I don't recall any more fixes and
> improvements for armv8-r.
> I would say I'm interested in target optimizations 😊
>
Sebastian. I don't know if you remember but Kinsey submitted all the useful
work for an R52 RTEMS BSP that unfortunately did not make it to silicon.
All RTEMS tests were passing on qemu. But since the project died, we didn't
feel that the BSP should be submitted.
We can coordinate off list if you want a snapshot of the remaining patches
that we haven't thought were worth submitting. They may be useful to you.
Note: I don't think we have any for newlib. The C implementations were
sufficient for as far as we for.
--joel
>
> Alex
>
> -----Original Message-----
> From: Newlib <newlib-bounces@sourceware.org> On Behalf Of Sebastian Huber
> Sent: Friday, 4 December, 2020 10:50 AM
> To: Newlib <newlib@sourceware.org>
> Subject: How well is the Arm Cortex-R52 supported by Newlib?
>
> Hello,
>
> it seems nobody used Newlib for the Arm Cortex-R52 before
>
> https://sourceware.org/pipermail/newlib/2020/018170.html
>
> ?
>
> How well is the Arm Cortex-R52 supported by the machine-specific files in
> Newlib in general? For example, memcpy() just uses the C implementation.
> Are there some improved/updated routines available from Arm which haven't
> been committed to Newlib? I can prepare the patches, I just need some hints
> were I can find the latest stuff.
>
> --
> 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:[~2020-12-07 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 7:49 Sebastian Huber
2020-12-07 16:31 ` Alexander Fedotov (OSS)
2020-12-07 16:52 ` Joel Sherrill [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=CAF9ehCVvHjF__UP9j0mpibXHvTNBB9GVwhovR3cu_mxcDvu02Q@mail.gmail.com \
--to=joel@rtems.org \
--cc=alexander.fedotov@oss.nxp.com \
--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).