From: Matias Garcia <mgarcia@rossvideo.com>
To: buildroot@busybox.net
Subject: [Buildroot] how to tune powerpc e500v2 cpus in BR
Date: Fri, 24 Jun 2011 13:31:26 -0400 [thread overview]
Message-ID: <4E04C9EE.4050206@rossvideo.com> (raw)
In-Reply-To: <BANLkTikRNGx1Mte+sOYDeOr9f896K8GuZw@mail.gmail.com>
Hi Raymond,
You can put those in the BR2_TARGET_OPTIMIZATIONS setting under the
Toolchain page e.g.
(-mcpu=8548 -mspe=yes -mabi=spe -mhard-float -mfloat-gprs=double)
Target Optimizations
I selected a generic powerpc target because I didn't need the -mtune
when I was specifying -mcpu already. As far as I know, 8548 and 8540
work out to the same code.
I switched to the external CodeSourcery build tools for two reasons: (1)
it allowed us to compile our application with -O3 (which we need) while
the standard GNU toolchain caused some errors, and (2) they're supported
by the Freescale/Mentor/CodeSourcery relationship, and not all of the
patches get applied to mainline (particularly for newer processors). I
had to add an option to the external wrapper so that it would call the
toolchain with '-te500v2' which is a shortcut for the optimizations you
list below. In that case, you can build your own applications without
calling any options explicitly.
Cheers,
Matias
On 11-06-24 10:27 AM, raymond zhao wrote:
> Hi,
> I am using freescale's p1020 CPU. It is a e500v2 core. How could I
> config the build root to tune the tool chain for the following
> options:
>
> -mcpu=8548 -mspe=yes -mabi=spe -mhard-float -mfloat-gprs=double
>
> From the menuconfig, I can only select CPU as 8540.
>
> Thanks,
>
> Raymond
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
next prev parent reply other threads:[~2011-06-24 17:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 14:27 [Buildroot] how to tune powerpc e500v2 cpus in BR raymond zhao
2011-06-24 17:31 ` Matias Garcia [this message]
2011-06-24 21:14 ` raymond zhao
2011-06-24 21:41 ` raymond zhao
2011-06-24 21:44 ` Bryan Hundven
2011-06-24 22:04 ` raymond zhao
2011-06-24 22:07 ` Bryan Hundven
2011-06-27 3:59 ` Baruch Siach
2011-06-27 20:10 ` raymond zhao
2011-06-27 20:23 ` Matias Garcia
2011-06-28 4:23 ` Baruch Siach
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=4E04C9EE.4050206@rossvideo.com \
--to=mgarcia@rossvideo.com \
--cc=buildroot@busybox.net \
/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