mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Jean-Claude Monnin <jc_monnin@emailplus.org>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] OSELAS Toolchain for ARM Cortex A5
Date: Thu, 16 Jul 2015 15:14:30 +0200	[thread overview]
Message-ID: <DC4FC207-CDE6-4B22-BF14-ABE296023519@emailplus.org> (raw)
In-Reply-To: <CABDcavb20OH_tyFEV25itqwTH+z-jKJw7p60VBEQWCCa8pS6zQ@mail.gmail.com>

Hi Guillermo,

> Can you provide some additional detail on why this had to be disabled?
> The arm-v7a-linux-gnueabihf toolchain also has "cortex-strings" in
> PTXCONF_GLIBC_EXTRA_ADDONS and so far it seems to work fine (although
> I have only been able to do limited testing)

With the "cortex-strings" enabled, it crashed somewhere in the boot process. I assumed this option provided some optimised functions using NEON instructions. However I never verified exactly what that option does. Maybe someone else can clarify?
What hardware do you use? SAMA5D3 lacks NEON instructions, but SAMA5D4 does support it.
'cortex-strings' seems to be enabled in the 'arm-v7a-linux-gnueabihf' of 'OSELAS toolchain 2013.12.2', but disabled in more recent versions of the toolchain.

Regards,
Jean-Claude
-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2015-07-16 11:14 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 [this message]
2015-07-16 13:27         ` Guillermo Rodriguez Garcia
2015-07-16 13:37           ` Michael Olbrich
2015-07-16 14:48             ` Guillermo Rodriguez Garcia
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=DC4FC207-CDE6-4B22-BF14-ABE296023519@emailplus.org \
    --to=jc_monnin@emailplus.org \
    --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