From: Markos Chandras <Markos.Chandras@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 02/11] arch: MIPS: Add config option BR2_GCC_TARGET_TUNE
Date: Mon, 7 Apr 2014 14:53:41 +0100 [thread overview]
Message-ID: <5342ADE5.1060908@imgtec.com> (raw)
In-Reply-To: <533DD7B6.8080009@crapouillou.net>
On 04/03/2014 10:50 PM, Paul Cercueil wrote:
> Hi Yann,
>
> This patch would pass the same value to --with-arch and --with-tune,
> unless you define a different value for BR2_GCC_TARGET_TUNE in your
> defconfig. We use that for the Ingenic jz4740 processor, which is a
> mips32 processor but running better the code tuned for mips32r2.
>
Hi Paul,
I don't understand this patch as well. If the jz4740 needs a mips32r2
userland, why not use Target Options-> Target Architecture Variant ->
mips32r2? You want to use the same toolchain for non-mips32r2 targets as
well?
The TARGET_TUNE option has been removed for MIPS in
f60dafe06833a17540608d1c8172d6535c513f1e
"arch/mips: Set BR2_GCC_TARGET_ARCH for MIPS"
and i see no good reason to bring it back.
If you need to optimize for a different ISA, wouldn't it be possible to
use custom CFLAGS in Toolchain->Target Optimizations?
--
markos
next prev parent reply other threads:[~2014-04-07 13:53 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 21:01 [Buildroot] [PATCH 01/11] toolchain: Make vendor configurable Paul Cercueil
2014-04-03 21:01 ` [Buildroot] [PATCH 02/11] arch: MIPS: Add config option BR2_GCC_TARGET_TUNE Paul Cercueil
2014-04-03 21:19 ` Yann E. MORIN
2014-04-03 21:50 ` Paul Cercueil
2014-04-03 22:12 ` Yann E. MORIN
2014-04-05 15:53 ` Paul Cercueil
2014-04-05 16:47 ` Yann E. MORIN
2014-04-07 13:53 ` Markos Chandras [this message]
2014-04-03 21:01 ` [Buildroot] [PATCH 03/11] gdb: Patch for "unrecognized real-time signal" bug Paul Cercueil
2014-10-12 14:06 ` Vincent Olivert Riera
2014-10-12 15:57 ` Thomas Petazzoni
2014-04-03 21:01 ` [Buildroot] [PATCH 04/11] gdb: Fix on-target threads debugging Paul Cercueil
2014-04-03 21:23 ` Yann E. MORIN
2014-04-03 21:01 ` [Buildroot] [PATCH 05/11] dialog: Patch incorrect use of toupper() Paul Cercueil
2014-04-03 21:32 ` Yann E. MORIN
2014-04-04 6:45 ` Arnout Vandecappelle
2014-04-08 16:56 ` Paul Cercueil
2014-04-10 8:40 ` Thomas De Schampheleire
2014-04-10 9:44 ` Arnout Vandecappelle
2014-07-19 14:06 ` Thomas De Schampheleire
2014-08-15 23:00 ` Paul Cercueil
2014-04-03 21:01 ` [Buildroot] [PATCH 06/11] libao: Remove OSS plugin when ALSA is enabled Paul Cercueil
2014-04-03 21:37 ` Yann E. MORIN
2014-04-03 21:01 ` [Buildroot] [PATCH 07/11] fmtools: Switch to 2.x series Paul Cercueil
2014-04-03 21:45 ` Yann E. MORIN
2014-04-06 13:26 ` Thomas Petazzoni
2014-04-03 21:01 ` [Buildroot] [PATCH 08/11] python-pygame: Make installation of examples optional Paul Cercueil
2014-04-03 21:48 ` Yann E. MORIN
2014-04-04 6:14 ` Arnout Vandecappelle
2014-04-03 21:01 ` [Buildroot] [PATCH 09/11] util-linux: Add config switches for some more binaries Paul Cercueil
2014-04-03 21:55 ` Yann E. MORIN
2014-04-03 22:00 ` Paul Cercueil
2014-04-03 21:01 ` [Buildroot] [PATCH 10/11] luajit: Allow to build on Mips and Mipsel platforms Paul Cercueil
2014-04-04 21:41 ` Thomas Petazzoni
2014-04-03 21:01 ` [Buildroot] [PATCH 11/11] stress: Patch to fix documentation source Paul Cercueil
2014-04-03 21:12 ` [Buildroot] [PATCH 01/11] toolchain: Make vendor configurable Yann E. MORIN
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=5342ADE5.1060908@imgtec.com \
--to=markos.chandras@imgtec.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