[ptxdist] OSELAS Toolchain for ARM Cortex A5

[ptxdist] OSELAS Toolchain for ARM Cortex A5

[Guillermo Rodriguez Garcia]

Hello all,

I am looking for a toolchain for Atmel SAMA5D3x series. These are ARM
Cortex A5 CPUs with hardware FPU.

I had a look at the latest OSELAS toolchain release (2014.12.1) and
didn't find a specific ptxconfig for Cortex A5. What would be the best
suitable? arm-v7a perhaps?

Does anybody have experience with OSELAS toolchain and the Atmel
SAMA5D3x series? (or otherwise with other Cortex A5 CPUs)?

Thank you,

Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] OSELAS Toolchain for ARM Cortex A5

[Jean-Claude Monnin]

[-- Attachment #1: Type: text/plain, Size: 2276 bytes --]

Hi,

> I am looking for a toolchain for Atmel SAMA5D3x series. These are ARM
> Cortex A5 CPUs with hardware FPU.
> 
> I had a look at the latest OSELAS toolchain release (2014.12.1) and
> didn't find a specific ptxconfig for Cortex A5. What would be the best
> suitable? arm-v7a perhaps?

I could boot the SAMA5D3-Xplained board using the 'arm-v7a-linux-gnueabihf’ config of OSELAS toolchain 2014.12.0.

> Does anybody have experience with OSELAS toolchain and the Atmel
> SAMA5D3x series? (or otherwise with other Cortex A5 CPUs)?


I’ve done a custom config based on the 'arm-cortexa8-linux-gnueabihf' toolchain. I had to remove the 'PTXCONF_GLIBC_EXTRA_ADDONS="cortex-strings”’ option. Please check the attached file and the diff’s.
Warning: I’m no expert in toolchains. Although it seems to run fine, I haven’t done much testing. It might be safer to go with the standard 'arm-v7a’ config.

Regards,
Jean-Claude



diff arm-cortexa5-linux-gnueabihf_gcc-4.9.2_glibc-2.20_binutils-2.24_kernel-3.16-sanitized.ptxconfig arm-cortexa8-linux-gnueabihf_gcc-4.9.2_glibc-2.20_binutils-2.24_kernel-3.16-sanitized.ptxconfig 
23c23
< PTXCONF_GNU_TARGET="arm-cortexa5-linux-gnueabihf"
---
> PTXCONF_GNU_TARGET="arm-cortexa8-linux-gnueabihf"
54c54
< PTXCONF_GLIBC_EXTRA_ADDONS=""
---
> PTXCONF_GLIBC_EXTRA_ADDONS="cortex-strings"
73c73
< PTXCONF_CROSS_GCC_CONFIG_EXTRA="--with-float=hard --with-fpu=vfpv4-d16 --with-cpu=cortex-a5 --with-mode=thumb"
---
> PTXCONF_CROSS_GCC_CONFIG_EXTRA="--with-float=hard --with-fpu=neon --with-cpu=cortex-a8 --with-mode=thumb"



diff arm-cortexa5-linux-gnueabihf_gcc-4.9.2_glibc-2.20_binutils-2.24_kernel-3.16-sanitized.ptxconfig arm-v7a-linux-gnueabihf_gcc-4.9.2_glibc-2.20_binutils-2.24_kernel-3.16-sanitized.ptxconfig 
23c23
< PTXCONF_GNU_TARGET="arm-cortexa5-linux-gnueabihf"
---
> PTXCONF_GNU_TARGET="arm-v7a-linux-gnueabihf"
50c50
< PTXCONF_GLIBC_CONFIG_EXTRA="--disable-multi-arch"
---
> PTXCONF_GLIBC_CONFIG_EXTRA=""
73c73
< PTXCONF_CROSS_GCC_CONFIG_EXTRA="--with-float=hard --with-fpu=vfpv4-d16 --with-cpu=cortex-a5 --with-mode=thumb"
---
> PTXCONF_CROSS_GCC_CONFIG_EXTRA="--with-float=hard --with-fpu=vfpv3-d16 --with-arch=armv7-a --with-mode=thumb --with-tune=cortex-a9"


[-- Attachment #2: arm-cortexa5-linux-gnueabihf_gcc-4.9.2_glibc-2.20_binutils-2.24_kernel-3.16-sanitized.ptxconfig --]
[-- Type: application/octet-stream, Size: 4253 bytes --]

#
# Automatically generated file; DO NOT EDIT.
# PTXdist 2014.12.0
#
PTXCONF__ptxconfig_MAGIC__=y
PTXCONF_BUILD_TOOLCHAIN=y
PTXCONF_NO_PLATFORM=y
PTXCONF_PROJECT="OSELAS.Toolchain-2014.12.0"

#
# ----------------------------------
#
PTXCONF_ARCH_ARM=y
# PTXCONF_ARCH_ARM64 is not set
# PTXCONF_ARCH_M68K is not set
# PTXCONF_ARCH_MIPS is not set
# PTXCONF_ARCH_POWERPC is not set
# PTXCONF_ARCH_I386 is not set
# PTXCONF_ARCH_X86_64 is not set
# PTXCONF_ARCH_AVR is not set
# PTXCONF_ARCH_AVR32 is not set
PTXCONF_ARCH="arm"
PTXCONF_GNU_TARGET="arm-cortexa5-linux-gnueabihf"
PTXCONF_SIZEOF_LONG_DOUBLE="8"

#
# ----------------------------------
#
PTXCONF_LIBC_HEADERS=y
PTXCONF_LIBC_FIRST=y
PTXCONF_LIBC=y
PTXCONF_LIBC_GLIBC=y
# PTXCONF_LIBC_UCLIBC is not set
# PTXCONF_LIBC_NEWLIB is not set
# PTXCONF_LIBC_MINGW is not set
# PTXCONF_LIBC_AVR is not set
PTXCONF_TOOLCHAIN_ENABLE_SYSROOT=y
PTXCONF_TOOLCHAIN_CONFIG_SYSROOT="--with-sysroot=${SYSROOT}"
PTXCONF_TOOLCHAIN_DISABLE_MULTILIB=y
PTXCONF_TOOLCHAIN_CONFIG_MULTILIB="--disable-multilib"
PTXCONF_GLIBC_HEADERS=y
PTXCONF_GLIBC_CRT=y
PTXCONF_GLIBC_FIRST=y
PTXCONF_GLIBC=y
PTXCONF_GLIBC_VERSION="2.20"
PTXCONF_GLIBC_MD5="5d9d375e670fe546a030061db36e9f3d"
PTXCONF_GLIBC_TIMESTAMP=""
PTXCONF_GLIBC_SERIES=""
PTXCONF_GLIBC_ENABLE_KERNEL="3.0"
PTXCONF_GLIBC_CONFIG_EXTRA="--disable-multi-arch"
PTXCONF_GLIBC_CONFIG_EXTRA_CROSS="--enable-obsolete-rpc"
PTXCONF_GLIBC_HEADERS_FAKE_CROSS="-D__ARM_EABI__"
PTXCONF_GLIBC_TLS=y
PTXCONF_GLIBC_EXTRA_ADDONS=""
# PTXCONF_GLIBC_PORTS is not set
PTXCONF_CROSS_BINUTILS=y
PTXCONF_CROSS_BINUTILS_VERSION="2.24"
PTXCONF_CROSS_BINUTILS_MD5="e0f71a7b2ddab0f8612336ac81d9636b"
# PTXCONF_CROSS_ELF2FLT is not set
PTXCONF_KERNEL_HEADERS=y
PTXCONF_KERNEL_HEADERS_VERSION="3.16"
PTXCONF_KERNEL_HEADERS_MD5="5c569ed649a0c9711879f333e90c5386"
PTXCONF_KERNEL_HEADERS_SANITIZED=y
PTXCONF_CROSS_GCC=y
PTXCONF_CROSS_GCC_VERSION="4.9.2"
PTXCONF_CROSS_GCC_MD5="4df8ee253b7f3863ad0b86359cd39c43"
PTXCONF_CROSS_GCC_DL_VERSION="${PTXCONF_CROSS_GCC_VERSION}"
PTXCONF_CROSS_GCC_PKGVERSION="${PTXCONF_PROJECT}"
PTXCONF_CROSS_GCC_43=y
PTXCONF_CROSS_GCC_45=y
PTXCONF_CROSS_GCC_48=y
PTXCONF_CROSS_GCC_SERIES=""
PTXCONF_CROSS_GCC_CONFIG_EXTRA="--with-float=hard --with-fpu=vfpv4-d16 --with-cpu=cortex-a5 --with-mode=thumb"

#
# Additional supported languages:
#
PTXCONF_CROSS_GCC_LANG_C=y
PTXCONF_CROSS_GCC_LANG_CXX=y
# PTXCONF_CROSS_GCC_LANG_FORTRAN is not set
# PTXCONF_CROSS_GCC_LANG_JAVA is not set
PTXCONF_CROSS_GCC_ENABLE_CXA_ATEXIT=y
PTXCONF_CROSS_GCC_CONFIG_CXA_ATEXIT="--enable-__cxa_atexit"
PTXCONF_CROSS_GCC_DISABLE_SJLJ_EXCEPTIONS=y
PTXCONF_CROSS_GCC_CONFIG_SJLJ_EXCEPTIONS="--disable-sjlj-exceptions"
PTXCONF_CROSS_GCC_DISABLE_LIBSSP=y
PTXCONF_CROSS_GCC_CONFIG_LIBSSP="--disable-libssp"
PTXCONF_CROSS_GCC_ENABLE_SHARED=y
PTXCONF_CROSS_GCC_CONFIG_SHARED="--enable-shared"
PTXCONF_CROSS_GCC_THREADS_POSIX=y
PTXCONF_CROSS_GCC_THREADS="posix"
PTXCONF_CROSS_GCC_FIRST=y
PTXCONF_CROSS_GDB=y
PTXCONF_CROSS_GDB_VERSION="7.8.1"
PTXCONF_CROSS_GDB_MD5="8072be87a94be0936bc3b4b6941b0862"
PTXCONF_CROSS_TOOLCHAIN=y
PTXCONF_HOST_FAKE_MAKEINFO=y
PTXCONF_HOST_CLOOG=y
PTXCONF_HOST_EXPAT=y
PTXCONF_HOST_GMP=y
PTXCONF_HOST_ISL=y
PTXCONF_HOST_MPC=y
PTXCONF_HOST_MPFR=y
PTXCONF_HOST_XZ=y
PTXCONF_HOST_ZLIB=y
PTXCONF_HOST_LIBELF=y
PTXCONF_HOST_AUTOTOOLS_AUTOCONF=y
PTXCONF_HOST_CHRPATH=y
PTXCONF_HOST_M4=y
PTXCONF_HOST_SYSTEM_PERL=y

#
# ----------------------------------
#

#
# misc                        
#
PTXCONF_PREFIX="/opt"
PTXCONF_PREFIX_KERNEL="-sanitized"
PTXCONF_PREFIX_TCID="gcc-${PTXCONF_CROSS_GCC_VERSION}${PTXCONF_PREFIX_JAVA}-glibc-${PTXCONF_GLIBC_VERSION}-binutils-${PTXCONF_CROSS_BINUTILS_VERSION}-kernel-${PTXCONF_KERNEL_HEADERS_VERSION}${PTXCONF_PREFIX_KERNEL}"
PTXCONF_SYSROOT_HOST="${PTXDIST_PLATFORMDIR}/sysroot-host"
PTXCONF_SYSROOT_CROSS="${PTX_AUTOBUILD_DESTDIR}${PTXCONF_PREFIX}/${PTXCONF_PROJECT}/${PTXCONF_GNU_TARGET}/${PTXCONF_PREFIX_TCID}"
PTXCONF_SYSROOT_TARGET="${PTXCONF_SYSROOT_CROSS}/sysroot-${PTXCONF_GNU_TARGET}"
PTXCONF_PLATFORM="${PTXCONF_GNU_TARGET}-${PTXCONF_PREFIX_TCID}"
PTXCONF_COMPILER_PREFIX="${PTXCONF_GNU_TARGET}-"
# PTXCONF_TOOLCHAIN_DEBUG is not set
PTXCONF_IMAGE_TOOLCHAIN_TGZ=y
PTXCONF_IMAGE_TOOLCHAIN_DEB=y
PTXCONF_CONFIGFILE_VERSION="2014.12.0"

[-- Attachment #3: Type: text/plain, Size: 2 bytes --]




[-- Attachment #4: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] OSELAS Toolchain for ARM Cortex A5

[Guillermo Rodriguez Garcia]

Hi Jean Claude,

2015-07-13 17:22 GMT+02:00 Jean-Claude Monnin <jc_monnin@emailplus.org>:
> Hi,
>
>> I am looking for a toolchain for Atmel SAMA5D3x series. These are ARM
>> Cortex A5 CPUs with hardware FPU.
>>
>> I had a look at the latest OSELAS toolchain release (2014.12.1) and
>> didn't find a specific ptxconfig for Cortex A5. What would be the best
>> suitable? arm-v7a perhaps?
>
> I could boot the SAMA5D3-Xplained board using the 'arm-v7a-linux-gnueabihf’ config of OSELAS toolchain 2014.12.0.

Great! Do you happen to have a working ptxdist config / BSP for this as well ?

>
>> Does anybody have experience with OSELAS toolchain and the Atmel
>> SAMA5D3x series? (or otherwise with other Cortex A5 CPUs)?
>
>
> I’ve done a custom config based on the 'arm-cortexa8-linux-gnueabihf' toolchain. I had to remove the 'PTXCONF_GLIBC_EXTRA_ADDONS="cortex-strings”’ option. Please check the attached file and the diff’s.

Thank you! This should be useful. I'll give this a try and give you
any useful feedback.

Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] OSELAS Toolchain for ARM Cortex A5

[Guillermo Rodriguez Garcia]

Hi Jean Claude,

2015-07-13 17:34 GMT+02:00 Guillermo Rodriguez Garcia
<guille.rodriguez@gmail.com>:
> Hi Jean Claude,
>
> 2015-07-13 17:22 GMT+02:00 Jean-Claude Monnin <jc_monnin@emailplus.org>:
>> Hi,
>>
>>> I am looking for a toolchain for Atmel SAMA5D3x series. These are ARM
>>> Cortex A5 CPUs with hardware FPU.
>>>
>>> I had a look at the latest OSELAS toolchain release (2014.12.1) and
>>> didn't find a specific ptxconfig for Cortex A5. What would be the best
>>> suitable? arm-v7a perhaps?
>>
>> I could boot the SAMA5D3-Xplained board using the 'arm-v7a-linux-gnueabihf’ config of OSELAS toolchain 2014.12.0.

I am now playing with arm-v7a-linux-gnueabihf (although I initially
used OSELAS toolchain 2013.12.2) and can confirm that this works fine
so far. This is without any changes or patches to the standard
toolchain configuration.

>
> Great! Do you happen to have a working ptxdist config / BSP for this as well ?
>
>>
>>> Does anybody have experience with OSELAS toolchain and the Atmel
>>> SAMA5D3x series? (or otherwise with other Cortex A5 CPUs)?
>>
>>
>> I’ve done a custom config based on the 'arm-cortexa8-linux-gnueabihf' toolchain. I had to remove the 'PTXCONF_GLIBC_EXTRA_ADDONS="cortex-strings”’ option. Please check the attached file and the diff’s.

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)

Thank you,

Guillermo Rodriguez Garcia
guille.rodriguez@gmail.com

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] OSELAS Toolchain for ARM Cortex A5

[Jean-Claude Monnin]

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

Re: [ptxdist] OSELAS Toolchain for ARM Cortex A5

[Guillermo Rodriguez Garcia]

Hello,

2015-07-16 15:14 GMT+02:00 Jean-Claude Monnin <jc_monnin@emailplus.org>:
> 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.

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.

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?

Thank you,

Guillermo

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] OSELAS Toolchain for ARM Cortex A5

[Michael Olbrich]

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.

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

Re: [ptxdist] OSELAS Toolchain for ARM Cortex A5

[Guillermo Rodriguez Garcia]

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

Re: [ptxdist] OSELAS Toolchain for ARM Cortex A5

[Michael Olbrich]

On Thu, Jul 16, 2015 at 03:14:30PM +0200, Jean-Claude Monnin wrote:
> > 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.

In the cortex-a8 toolchains we have 'cortex-strings'. These are string
funtions that use NEON instructions unconditionally and are (in the version
we use here) optimized for cortex-a8.

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.

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

Re: [ptxdist] OSELAS Toolchain for ARM Cortex A5

[Guillermo Rodriguez Garcia]

Hi Michael,

2015-07-16 15:30 GMT+02:00 Michael Olbrich <m.olbrich@pengutronix.de>:
> In the cortex-a8 toolchains we have 'cortex-strings'. These are string
> funtions that use NEON instructions unconditionally and are (in the version
> we use here) optimized for cortex-a8.

Uhm. So I guess that the toolchain I am using (arm-v7a-linux-gnueabihf
from OSELAS.Toolchain-2013.12.2) shouldn't actually work. For some
reason I haven't seen any problem yet.

>
> 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
?

Thanks,

Guillermo

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] OSELAS Toolchain for ARM Cortex A5

[Michael Olbrich]

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