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 12:11:47 +0100	[thread overview]
Message-ID: <20140223121147.3c24dde4@skate> (raw)
In-Reply-To: <884EA965490E3C4D8E66AEF41E98025006C2AD@ezex10.ezchip.com>

Dear Noam Camus,

(It would be nice if you could avoid top-posting. It is considered a
bad practice in most open-source circles. See
http://en.wikipedia.org/wiki/Posting_style#Top-posting vs.
http://en.wikipedia.org/wiki/Posting_style#Bottom-posting. Thanks!)

On Sun, 23 Feb 2014 10:57:06 +0000, Noam Camus wrote:

> Using external toolchain than BR2_GCC_TARGET_CPU is passed to GCC by -mcpu 
> Using buildroot toolchain than BR2_GCC_TARGET_CPU is passed to configure by --with-cpu

Passing -mcpu or --with-cpu is already taken care of by Buildroot
depending on the case. However, normally, gcc accepts the same
possible values for both -mcpu and --with-cpu.

> ARC GCC likes to get -mcpu=ARC700
> However through configure I am not sure but I think that config.gcc script is involved and it likes to get arc*.
> 
> Maybe my patch is a workaround to make external toolchain work for ARC and complete solution is to change ARC GCC.

I'm Cc'ing Anton, from Synposys, to get more details about this.

Noam, which ARC external toolchain are you using? Maybe it's an older
ARC toolchain, and Synopsys has since then changed the possible -mcpu
values?

Best regards,

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

  parent reply	other threads:[~2014-02-23 11:11 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
2014-02-23 10:57   ` Noam Camus
2014-02-23 11:09     ` Yann E. MORIN
2014-02-23 11:11     ` Thomas Petazzoni [this message]
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=20140223121147.3c24dde4@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