From: Shinya Kuribayashi <skuribay@pobox.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 3/5] MIPS: Optimize the setup of endianess and CPU optimization flags
Date: Mon, 28 Mar 2011 23:56:40 +0900 [thread overview]
Message-ID: <4D90A1A8.1030404@pobox.com> (raw)
In-Reply-To: <AANLkTimPROXMwZ01a60s+KcWg6kLmgvWQK7hxyY3p3-T@mail.gmail.com>
Sorry for being late,
On 03/24/2011 01:37 AM, Daniel Schwierzeck wrote:
> 2011/3/23 Shinya Kuribayashi <skuribay@pobox.com>:
> Following changes have been introduced to ld in binutils-2.16:
[...]
> I'd claim that all toolchains with binutils lesser than 2.16 are not
> working anymore.
[...]
>>> I suggest to drop official support for ELDK-3.1.1 / binutils-2.14 and
>>> earlier.
Excellent, no comments from me. Let's forget about all pre-binutils
2.16 releases from now on, and ELDK-3.1.1 as well.
> I have prepared a v3 of this patch that checks whether -mips32r2 is
> supported. If not than -mips32 will be used as fallback. But I want
> to clarify this first before I send it.
I'm guessting you're worried that the corresponding line will differ
from what the Linux/MIPS has, but that's not a problem. The Linux/MIPS
tries to tighten the condition in accordance with explicit configuration
options such as CONFIG_CPU_MIPS32_R1/R2, CONFIG_CPU_MIPS64_R1/R2.
> cflags-$(CONFIG_CPU_MIPS32_R1) += $(call cc-option,-march=mips32,-mips32 -U_MIPS_ISA -D_MIPS_ISA=_MIPS_ISA_MIPS32) \
> -Wa,-mips32 -Wa,--trap
> cflags-$(CONFIG_CPU_MIPS32_R2) += $(call cc-option,-march=mips32r2,-mips32r2 -U_MIPS_ISA -D_MIPS_ISA=_MIPS_ISA_MIPS32) \
> -Wa,-mips32r2 -Wa,--trap
> cflags-$(CONFIG_CPU_MIPS64_R1) += $(call cc-option,-march=mips64,-mips64 -U_MIPS_ISA -D_MIPS_ISA=_MIPS_ISA_MIPS64) \
> -Wa,-mips64 -Wa,--trap
> cflags-$(CONFIG_CPU_MIPS64_R2) += $(call cc-option,-march=mips64r2,-mips64r2 -U_MIPS_ISA -D_MIPS_ISA=_MIPS_ISA_MIPS64) \
> -Wa,-mips64r2 -Wa,--trap
We U-Boot doesn't have to follow this convention, and can relax the cc-
option rules.
I'll wait for v3 patch(es), and push them during the next merge window.
Thanks in advance,
next prev parent reply other threads:[~2011-03-28 14:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 21:14 [U-Boot] [PATCH v2 0/5] MIPS: Refactoring of CPU and SoC code daniel.schwierzeck at googlemail.com
2011-03-14 21:14 ` [U-Boot] [PATCH v2 1/5] MIPS: Purple: Remove Purple support daniel.schwierzeck at googlemail.com
2011-03-14 21:14 ` [U-Boot] [PATCH v2 2/5] MIPS: Move content of arch/mips/cpu to arch/mips/cpu/mips32 daniel.schwierzeck at googlemail.com
2011-03-14 21:14 ` [U-Boot] [PATCH v2 3/5] MIPS: Optimize the setup of endianess and CPU optimization flags daniel.schwierzeck at googlemail.com
2011-03-14 23:54 ` Shinya Kuribayashi
2011-03-15 13:20 ` Daniel Schwierzeck
2011-03-16 13:18 ` Shinya Kuribayashi
2011-03-16 14:41 ` Daniel Schwierzeck
2011-03-17 14:02 ` Shinya Kuribayashi
2011-03-17 15:20 ` Daniel Schwierzeck
2011-03-21 12:42 ` Daniel Schwierzeck
2011-03-23 14:51 ` Shinya Kuribayashi
2011-03-23 16:37 ` Daniel Schwierzeck
2011-03-28 14:56 ` Shinya Kuribayashi [this message]
2011-03-28 15:27 ` Daniel Schwierzeck
2011-03-28 15:58 ` Shinya Kuribayashi
2011-03-28 16:11 ` Daniel Schwierzeck
2011-03-14 21:14 ` [U-Boot] [PATCH v2 4/5] MIPS: IncaIP: Move all IncaIP specific code to separate subdirectory daniel.schwierzeck at googlemail.com
2011-03-14 21:14 ` [U-Boot] [PATCH v2 5/5] MIPS: Au1x00: Move all Au1x00 " daniel.schwierzeck at googlemail.com
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=4D90A1A8.1030404@pobox.com \
--to=skuribay@pobox.com \
--cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.