From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ARC: Add support for ARC HS38 with Hardware Floating Point
Date: Mon, 10 Jul 2017 15:46:29 +0200 [thread overview]
Message-ID: <20170710154629.442a4411@windsurf.lan> (raw)
In-Reply-To: <20170710133650.8692-1-abrodkin@synopsys.com>
Hello,
On Mon, 10 Jul 2017 16:36:50 +0300, Alexey Brodkin wrote:
> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> ---
> arch/Config.in.arc | 10 +++++++---
> package/uclibc/Config.in | 1 +
> 2 files changed, 8 insertions(+), 3 deletions(-)
>
> diff --git a/arch/Config.in.arc b/arch/Config.in.arc
> index 7d341f3136..d0e2286557 100644
> --- a/arch/Config.in.arc
> +++ b/arch/Config.in.arc
> @@ -14,12 +14,15 @@ config BR2_arc770d
> config BR2_archs38
> bool "ARC HS38"
>
> +config BR2_archs38_hf
> + bool "ARC HS38 with hard floating-point"
Does it need to be a separate CPU type, or an option when HS38 is
selected ?
> config BR2_ARCH
> default "arc" if BR2_arcle
> @@ -37,6 +40,7 @@ config BR2_GCC_TARGET_CPU
> default "arc700" if BR2_arc750d
> default "arc700" if BR2_arc770d
> default "archs" if BR2_archs38
> + default "hs38_linux" if BR2_archs38_hf
gcc really understands -mcpu=hs38_linux ?
It seems odd to have the operating system name encoded in the CPU name.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-07-10 13:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 13:36 [Buildroot] [PATCH] ARC: Add support for ARC HS38 with Hardware Floating Point Alexey Brodkin
2017-07-10 13:46 ` Thomas Petazzoni [this message]
2017-07-10 14:05 ` Alexey Brodkin
2018-03-31 14:38 ` Arnout Vandecappelle
2018-04-02 13:19 ` Alexey Brodkin
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=20170710154629.442a4411@windsurf.lan \
--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 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.