Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Cercueil <paul@crapouillou.net>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 02/11] arch: MIPS: Add config option BR2_GCC_TARGET_TUNE
Date: Sat, 05 Apr 2014 17:53:55 +0200	[thread overview]
Message-ID: <53402713.9070801@crapouillou.net> (raw)
In-Reply-To: <20140403221215.GA25471@free.fr>

Hi,

On 04/04/2014 00:12, Yann E. MORIN wrote:
> Paul, All,
>
> On 2014-04-03 23:50 +0200, Paul Cercueil spake thusly:
>> 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.
> I see what you expect, but since BR2_GCC_TARGET_TUNE is a prompt-less
> option, setting it in a defconfig will be overriden when you use that
> defconfig.
>
> For example:
>
>      $ cat defconfig
>      BR2_MIPS=y
>      BR2_GCC_TARGET_ARCH="FOO-YEM"
>      $ make BR2_DEFCONFIG=$(pwd)/defconfig defconfig
>      [...]
>      $ grep FOO .config
>      [empty, nada, zilch]
>
> So, even if you set it in your defconfig, BR2_GCC_TARGET_ARCH is lost.
>
> Ditto for BR2_GCC_TARGET_TUNE.
>
>> We
>> use that for the Ingenic jz4740 processor, which is a mips32 processor but
>> running better the code tuned for mips32r2.
> Oh, I see. But that's not gonna happen with this code, I'm afraid.
>
> Can you double-check that it is indeed working for you? Because if it
> does, we have a really big bug in Kconfig (Oh, no, not one more...)
>
> Regards,
> Yann E. MORIN.

I confirm it works. Why is it a bug?

Paul
>
>> On 03/04/2014 23:19, Yann E. MORIN wrote:
>>> Paul, All,
>>>
>>> On 2014-04-03 23:01 +0200, Paul Cercueil spake thusly:
>>>> This option is actually already used in GCC's package.
>>>>
>>>> This allows to optimize the toolchain for a specific MIPS processor
>>>> while supporting more than one family of processors.
>>> Is that really needed? man gcc says:
>>>
>>>      When this option is not used, GCC optimizes for the processor
>>>      specified by -march.
>>>
>>> Since this patch would pass the same value to --with-arch and
>>> --with-tune, and since this is the default of gcc, is it really
>>> needed?
>>>
>>> Neither ACKing nor NAKing this patch. Can you explain a bit more why we
>>> would want that, given the above explanations?
>>>
>>> Regards,
>>> Yann E. MORIN.
>>>
>>>> Signed-Off-By: Paul Cercueil <paul@crapouillou.net>
>>>> ---
>>>>   arch/Config.in.mips | 10 ++++++++++
>>>>   1 file changed, 10 insertions(+)
>>>>
>>>> diff --git a/arch/Config.in.mips b/arch/Config.in.mips
>>>> index 20951e0..e4160a2 100644
>>>> --- a/arch/Config.in.mips
>>>> +++ b/arch/Config.in.mips
>>>> @@ -83,6 +83,16 @@ config BR2_GCC_TARGET_ARCH
>>>>   	default "mips64"	if BR2_mips_64
>>>>   	default "mips64r2"	if BR2_mips_64r2
>>>> +config BR2_GCC_TARGET_TUNE
>>>> +	default "mips1"		if BR2_mips_1
>>>> +	default "mips2"		if BR2_mips_2
>>>> +	default "mips3"		if BR2_mips_3
>>>> +	default "mips4"		if BR2_mips_4
>>>> +	default "mips32"	if BR2_mips_32
>>>> +	default "mips32r2"	if BR2_mips_32r2
>>>> +	default "mips64"	if BR2_mips_64
>>>> +	default "mips64r2"	if BR2_mips_64r2
>>>> +
>>>>   config BR2_MIPS_OABI32
>>>>   	bool
>>>>   	default y		if BR2_mips || BR2_mipsel
>>>> -- 
>>>> 1.9.0
>>>>
>>>> _______________________________________________
>>>> buildroot mailing list
>>>> buildroot at busybox.net
>>>> http://lists.busybox.net/mailman/listinfo/buildroot

  reply	other threads:[~2014-04-05 15: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 [this message]
2014-04-05 16:47           ` Yann E. MORIN
2014-04-07 13:53       ` Markos Chandras
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=53402713.9070801@crapouillou.net \
    --to=paul@crapouillou.net \
    --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