I'd noticed that the cortexa8 toolchain was not available when I was starting 
to set up a new test build-environment with the latest versions.  We're using 
the TI AM3352.

 - Jason

-----Original Message-----
From: ptxdist [mailto:ptxdist-boun...@pengutronix.de] On Behalf Of Michael 
Sent: Monday, April 09, 2018 4:41 AM
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Including valgrind in the configuration doesn't trigger 
an un-optimized build of glibc.


On Thu, Apr 05, 2018 at 02:41:38PM -0500, Crim, Jason wrote:
> I've got my toolchain switched to the arm-v7a-linux-gnueabihf (from 
> the arm-cortexa8-linux-gnueabihf), and valgrind is now working.  It 
> complains about _armv7_tick being an unrecognized instruction, but my 
> program does continue to run (in defiance of valgrind's warning message).
> Long term, what are the trade-offs for using the v7a vs. the cortexa8 
> toolchains in production?  I do not know the history of the decision 
> in my organization, but the cortex toolchain was in place before my 
> arrival.  I'm trying to decide whether to keep the change local on my 
> dev/debug system, or suggest a migration.

I recommend using v7a. It uses the same settings as most armhf distributions, 
so this has better test coverage. I actually dropped the
cortexa8 toolchain from the latest OSELAS.Toolchain release.
It may be a bit slower depending on your hardware. What's your cpu anyways?


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 mailing list

Reply via email to