Hi Guillermo, On Thu, Mar 02, 2017 at 03:50:19PM +0100, Guillermo Rodriguez Garcia wrote: > Hi Alexander, > > Thank you for your answer. > > 2017-03-01 22:03 GMT+01:00 Alexander Dahl <p...@lespocky.de>: > > Hei hei, > > > > On Wed, Mar 01, 2017 at 06:36:38PM +0100, Guillermo Rodriguez Garcia wrote: > >> Is someone using ptxdist with iMX6 based targets? I know phytec used > >> ptxdist in the past but now they seem to be using Yocto instead.
We use PTXdist for an i.MX6Q based target. The toolchain we use is based on OSELAS.Toolchain, but I updated it to use the most recent GCC 6.3.0, glibc 2.25, binutils 2.27, gdb 7.12.1, kernel-headers, etc. Also changed some configure options to enable a few additional features and improve the reproducability of builds. Besides that, I also added a few patches from the buildroot project. Not sure if it is upstreamable because I can't test if the other ptxconfigs still work and I only ever used it for our i.MX6Q board. But if you are interested I could send a few patches or create a GitHub repo to work on it. > That is a great start. Some things that draw my attention, though: > > - VFPv3-D16 selected whereas iMX6 can do VFPv3-D32 (or just "VFPv3") For the i.MX6 you can use the full VFPv3-D32 but I'd recommend using -mfpu=neon instead. Performance is a little bit better than with -mfpu=vfpv3. > - Thumb mode used by default (not sure why -- wouldn't it be more > appropriate to use arm mode by default unless there is an explicit > intent to optimize size over speed ?) Yes, the performance is better than with Thumb 2. (Maybe related to the conditional execution feature in the original ARM instruction set.. still being faster than the use of the IT instruction in Thumb-2?) Space and memory are not the biggest concerns on our board (4GB eMMC, 1GB RAM), so using ARM mode made sense and works great. Regards, Clemens _______________________________________________ ptxdist mailing list ptxdist@pengutronix.de
