From: Guillermo Rodriguez Garcia <guille.rodriguez@gmail.com>
To: "ptxdist@pengutronix.de" <ptxdist@pengutronix.de>
Subject: Re: [ptxdist] OSELAS Toolchain for ARM Cortex A5
Date: Thu, 16 Jul 2015 16:48:39 +0200 [thread overview]
Message-ID: <CABDcavY8_13Ek2C_n7QvL8BVdVcX9Xx7BE-wP1cRWcLa-wqRtQ@mail.gmail.com> (raw)
In-Reply-To: <20150716133752.GC27933@pengutronix.de>
Hi Michael,
2015-07-16 15:37 GMT+02:00 Michael Olbrich <m.olbrich@pengutronix.de>:
> On Thu, Jul 16, 2015 at 03:27:57PM +0200, Guillermo Rodriguez Garcia wrote:
>> 2015-07-16 15:14 GMT+02:00 Jean-Claude Monnin <jc_monnin@emailplus.org>:
>> Uhm. I am using a SAMA5D3 Xplained board (so no NEON). However
>> Linaro's README file for the cortex-strings project states that these
>> should also be available for CPUs without NEON support:
>> https://git.linaro.org/toolchain/cortex-strings.git/blob/HEAD:/README
>>
>> As stated, I used the arm-v7a-linux-gnueabihf from
>> OSELAS.Toolchain-2013.12.2 without any modifications or changes and
>> the system boots and seems to work just fine. I'll keep an eye on
>> this.
>
> If the cortex-strings are actually used, then any memcpy should crash.
> However, it is quite possible that these where ignored by the glibc
> build system for ARM v7a. I don't remember the details here. Something like
> that happend with some version but I don't remember which.
>
>> It would be good to konw why cortex-strings was disabled in more
>> recent versions of the OSELAS.Toolchain. Can someone shed some light
>> here?
>
> As a said in my other mail glibc no includes a newer version of this code.
> I left it there for cortex-a8 because my benchmarks showed that the new
> versions did not perform very well there.
> I'll revisit the topic for the next major toolchain version.
Thank you very much; this is clear now.
Guillermo
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2015-07-16 12:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 14:39 Guillermo Rodriguez Garcia
2015-07-13 15:22 ` Jean-Claude Monnin
2015-07-13 15:34 ` Guillermo Rodriguez Garcia
2015-07-16 11:43 ` Guillermo Rodriguez Garcia
2015-07-16 13:14 ` Jean-Claude Monnin
2015-07-16 13:27 ` Guillermo Rodriguez Garcia
2015-07-16 13:37 ` Michael Olbrich
2015-07-16 14:48 ` Guillermo Rodriguez Garcia [this message]
2015-07-16 13:30 ` Michael Olbrich
2015-07-16 13:36 ` Guillermo Rodriguez Garcia
2015-07-16 13:39 ` Michael Olbrich
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=CABDcavY8_13Ek2C_n7QvL8BVdVcX9Xx7BE-wP1cRWcLa-wqRtQ@mail.gmail.com \
--to=guille.rodriguez@gmail.com \
--cc=ptxdist@pengutronix.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