mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: "Crim, Jason" <jason.crim@thyssenkrupp.com>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] Including valgrind in the configuration doesn't trigger an un-optimized build of glibc.
Date: Mon, 9 Apr 2018 07:13:00 -0500	[thread overview]
Message-ID: <2D79272AFFD75A4392ED2D3EF16D3B53B52535@mdcxch20.na.ops.local> (raw)
In-Reply-To: <20180409084112.6d6u7qvvsmbjsktz@pengutronix.de>

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.

Thanks,
 - Jason

-----Original Message-----
From: ptxdist [mailto:ptxdist-bounces@pengutronix.de] On Behalf Of Michael Olbrich
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.

Hi,

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?

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
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2018-04-09 12:14 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-28 10:01 Andrej.Gantvorg
2018-03-28 15:43 ` Crim, Jason
2018-03-29  9:20   ` Michael Olbrich
2018-04-05 19:41     ` Crim, Jason
2018-04-09  8:41       ` Michael Olbrich
2018-04-09 12:13         ` Crim, Jason [this message]
2018-04-09 13:49           ` Michael Olbrich
  -- strict thread matches above, loose matches on Subject: below --
2018-03-22 17:38 Crim, Jason
2018-03-26  6:30 ` Michael Olbrich
2018-03-26 12:03   ` Crim, Jason
2018-03-27  7:33     ` Michael Olbrich
2018-03-27 11:54       ` Crim, Jason

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=2D79272AFFD75A4392ED2D3EF16D3B53B52535@mdcxch20.na.ops.local \
    --to=jason.crim@thyssenkrupp.com \
    --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