From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] OSELAS Toolchain for ARM Cortex A5
Date: Thu, 16 Jul 2015 15:39:29 +0200 [thread overview]
Message-ID: <20150716133929.GD27933@pengutronix.de> (raw)
In-Reply-To: <CABDcavYsSLAiUodn7t4LoHZnnGxiaJpj9Mhd1q9Zr7d1TQuR4w@mail.gmail.com>
On Thu, Jul 16, 2015 at 03:36:41PM +0200, Guillermo Rodriguez Garcia wrote:
> > A newer version of these functions reached mainline in gcc-4.9. There are
> > optimized for cortex-a9. Also, NEON support is detected at runtime and
> > approriate versions of the functions are selected. This is what we use in
> > the arm-v7a-linux-gnueabihf toolchain since OSELAS.Toolchain-2014.12.0.
>
> However I just peeked at OSELAS.Toolchain-2014.12.1 and there is no
> trace of cortex-strings in
> arm-v7a-linux-gnueabihf_gcc-4.9.2_glibc-2.20_binutils-2.24_kernel-3.16-sanitized.ptxconfig
> (PTXCONF_GLIBC_EXTRA_ADDONS is empty). Am I looking in the wrong place
> ?
The upstream version is enabled automatically, so no config option is
needed.
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
--
ptxdist mailing list
ptxdist@pengutronix.de
prev parent reply other threads:[~2015-07-16 11:39 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
2015-07-16 13:30 ` Michael Olbrich
2015-07-16 13:36 ` Guillermo Rodriguez Garcia
2015-07-16 13:39 ` Michael Olbrich [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=20150716133929.GD27933@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--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