From: Michael Olbrich <m.olbrich@pengutronix.de>
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 15:49:39 +0200 [thread overview]
Message-ID: <20180409134939.zrz2jyeu2pswxf5z@pengutronix.de> (raw)
In-Reply-To: <2D79272AFFD75A4392ED2D3EF16D3B53B52535@mdcxch20.na.ops.local>
On Mon, Apr 09, 2018 at 07:13:00AM -0500, Crim, Jason wrote:
> 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.
The v7a toolchain works just fine with this CPU. You can add
'-mcpu=cortex-a8 -mfpu=neon' to TARGET_EXTRA_CFLAGS/CXXFLAGS. This way,
the rest of the BSP will be compiled with the same optimizations as before.
But you probably won't notice the difference.
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
next prev parent reply other threads:[~2018-04-09 13:49 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
2018-04-09 13:49 ` Michael Olbrich [this message]
-- 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=20180409134939.zrz2jyeu2pswxf5z@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