Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] external toolchain: [ARC] gcc cpu parameter
Date: Sun, 23 Feb 2014 10:48:07 +0100	[thread overview]
Message-ID: <20140223104807.473b5d47@skate> (raw)
In-Reply-To: <884EA965490E3C4D8E66AEF41E98025006BF3A@ezex10.ezchip.com>

Dear Noam Camus,

On Sun, 23 Feb 2014 08:28:55 +0000, Noam Camus wrote:
> external toolchain passes -mcpu=arc700
> However compiler is familiar with -mcpu=ARC700
> 
> Signed-off-by: Noam Camus <noamc@ezchip.com>
> ---
>  arch/Config.in.arc |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/arch/Config.in.arc b/arch/Config.in.arc index 60b59f0..53e7052 100644
> --- a/arch/Config.in.arc
> +++ b/arch/Config.in.arc
> @@ -11,4 +11,5 @@ config BR2_ENDIAN
>  	default "BIG"	 if BR2_arceb
>  
>  config BR2_GCC_TARGET_CPU
> +	default "ARC700" if BR2_TOOLCHAIN_EXTERNAL
>  	default "arc700"

We clearly don't want to use BR2_TOOLCHAIN_EXTERNAL here as a
condition. What is the official value? Is it -mcpu=arc700 or
-mcpu=ARC700 ? Maybe the existing arc700 value was wrong and should
just be fixed? Or does the value depends on the gcc version?

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-02-23  9:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-23  8:28 [Buildroot] [PATCH] external toolchain: [ARC] gcc cpu parameter Noam Camus
2014-02-23  9:48 ` Thomas Petazzoni [this message]
2014-02-23 10:57   ` Noam Camus
2014-02-23 11:09     ` Yann E. MORIN
2014-02-23 11:11     ` Thomas Petazzoni
2014-02-24  1:43       ` Anton Kolesov
2014-08-03 13:01 ` Thomas Petazzoni

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=20140223104807.473b5d47@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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