From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: move -march=* and -mtune= options to arch/arm/Makefile
Date: Wed, 25 Feb 2015 22:14:36 +0100 [thread overview]
Message-ID: <20150225221436.2c21b6fd@lilith> (raw)
In-Reply-To: <1423565576-30484-1-git-send-email-yamada.m@jp.panasonic.com>
Hello Masahiro,
On Tue, 10 Feb 2015 19:52:56 +0900, Masahiro Yamada
<yamada.m@jp.panasonic.com> wrote:
> My main motivation for this commit:
>
> [1] Follow the arch/arm/Makefile style of Linux Kernel
>
> [2] Maintain compiler options systematically
> Currently, we give -march=* and -mtune=* options inconsistently:
> Only some of the CPUs pass -march=* and -mtune=* options.
> By collecting flags into the arch/arm/Makefile, we can tell which
> options are missing at a glance.
>
> [3] Prepare for deprecating arch/*/cpu/*/config.mk
>
> Note:
> This commit just moves the compiler options so as not to change
> the behavior at all. It does not care the correctness of the
> given options. Fox example, "-march=armv5te" might be better than
> "-march=armv4" for ARM946EJS, but it is beyond the scope this
> commit. Also, filling the missing -march=* and -tune=* is left
> to follow-up patches.
>
> Signed-off-by: Masahiro Yamada <yamada.m@jp.panasonic.com>
> ---
I'm fine with the patch's goal and principle, but it does not seem to
apply properly to u-boot-arm/master. Can you have a look?
Amicalement,
--
Albert.
next prev parent reply other threads:[~2015-02-25 21:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 10:52 [U-Boot] [PATCH] ARM: move -march=* and -mtune= options to arch/arm/Makefile Masahiro Yamada
2015-02-10 11:00 ` Marek Vasut
2015-02-10 12:05 ` Stefan Roese
2015-02-25 21:14 ` Albert ARIBAUD [this message]
2015-02-26 17:43 ` Masahiro YAMADA
2015-03-13 11:54 ` Masahiro Yamada
2015-04-02 6:58 ` Albert ARIBAUD
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=20150225221436.2c21b6fd@lilith \
--to=albert.u.boot@aribaud.net \
--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