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: Thu, 17 Mar 2011 23:02:49 +0900 [thread overview]
Message-ID: <4D821489.50802@pobox.com> (raw)
In-Reply-To: <AANLkTi=YKYR+eXELrQL6AxJcwfxftwOk7D+rQ_MYQ=yw@mail.gmail.com>
On 03/16/2011 11:41 PM, Daniel Schwierzeck wrote:
> Is my approach with -march acceptable? This is more important to me
> for supporting new SoCs with 24k and 34k CPU cores. I think its a
> clean approach to use a default Mips32 architecture optimization plus
> a per CPU optimization configured in the SoC directories.
IIUC this is a binutils related issue.
> @@ -20,20 +20,13 @@
> # Foundation, Inc., 59 Temple Place, Suite 330, Boston,
> # MA 02111-1307 USA
> #
> -v=$(shell $(AS) --version | grep 'GNU assembler' | egrep -o '2\.[0-9\.]+' | cut -d. -f2)
> -MIPSFLAGS:=$(shell \
> -if [ "$v" -lt "14" ]; then \
> - echo "-mcpu=4kc"; \
> -else \
> - echo "-march=4kc -mtune=4kc"; \
> -fi)
>
> [...]
> +# Optimization flags for all Mips32 CPUs
> +MIPSFLAGS = $(call cc-option,-march=mips32r2,-mips32r2 -Wa,-mips32r2)
According to GNU gas NEWS, mips32r2 support was introduced in 2.14:
http://sourceware.org/cgi-bin/cvsweb.cgi/~checkout~/src/gas/NEWS?rev=1.117&content-type=text/plain&cvsroot=src&only_with_tag=binutils-binutils-2_21
On the other hand, we have a number of the ELDK releases so far, and
their binutils versions vary from 2.11 (ELDK2.1.0) to 2.16.1 (ELDK4.1).
2.1.0: http://mirror.switch.ch/ftp/mirror/eldk/2.1.0/eldk-mips-linux-x86/README.html
3.0: (N/A for MIPS?)
3.1: http://mirror.switch.ch/ftp/mirror/eldk/3.1/mips-linux-x86/distribution/README.html
3.1.1: http://mirror.switch.ch/ftp/mirror/eldk/3.1.1/mips-linux-x86/distribution/README.html
4.0: http://mirror.switch.ch/ftp/mirror/eldk/4.0/mips-linux-x86/distribution/README.html
http://www.denx.de/en/News/PressReleaseELDK40
4.1: http://mirror.switch.ch/ftp/mirror/eldk/4.1/mips-linux-x86/distribution/README.html
http://www.denx.de/en/News/PressReleaseELDK41
4.2: (N/A for MIPS?)
Does above change break any builds with older binutils? Personally, I'm
ok with dropping older toolchains to some extent. However, if it breaks
builds with older toolchains, strictly speaking older versions of the
ELDK releases, the decision is up to Wolfgang.
Along with the code, it'd be nice to provide a note in the git commit
log about which ELDK version(s) will be affected by this change. I'm
not sure that anyone still uses the ELSK2.1.0 in the wild, nor current
U-Boot/MIPS can be built with it, though.
next prev parent reply other threads:[~2011-03-17 14:02 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 [this message]
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
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=4D821489.50802@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox