All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: move -march=* and -mtune= options to arch/arm/Makefile
Date: Tue, 10 Feb 2015 12:00:33 +0100	[thread overview]
Message-ID: <201502101200.33116.marex@denx.de> (raw)
In-Reply-To: <1423565576-30484-1-git-send-email-yamada.m@jp.panasonic.com>

On Tuesday, February 10, 2015 at 11:52:56 AM, Masahiro Yamada 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>

Very nice,

Acked-by: Marek Vasut <marex@denx.de>

Best regards,
Marek Vasut

  reply	other threads:[~2015-02-10 11:00 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 [this message]
2015-02-10 12:05 ` Stefan Roese
2015-02-25 21:14 ` Albert ARIBAUD
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=201502101200.33116.marex@denx.de \
    --to=marex@denx.de \
    --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.