From: Vineet Gupta <Vineet.Gupta1@synopsys.com>
To: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>,
"linux-snps-arc@lists.infradead.org"
<linux-snps-arc@lists.infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Alexey Brodkin" <Alexey.Brodkin@synopsys.com>
Subject: Re: [PATCH 1/3] ARC: allow to overide default mcpu compiler flag
Date: Fri, 29 May 2020 20:47:17 +0000 [thread overview]
Message-ID: <c1dee77e-f8e3-1213-61a9-390412bfb5ee@synopsys.com> (raw)
In-Reply-To: <20200529115534.22883-2-Eugeniy.Paltsev@synopsys.com>
On 5/29/20 4:55 AM, Eugeniy Paltsev wrote:
> By default we set -mcpu=xxx compiler flag depending on the CPU ISA
> version. It's good starting point, however that may be not enough
> as for some platforms we may want to use some specific 'mcpu'
> options for better optimization or to workaround HW issues.
>
> We are going to use this option for HSDK-4xD board support.
> In addition it also allows to awoid patching 'mcpu' in ARC Makefile
> when we building Linux for some non-standard simulation or FPGA-based
> platforms.
>
> Signed-off-by: Eugeniy Paltsev <Eugeniy.Paltsev@synopsys.com>
Question: So now if I build in buildroot with -mhs38_linux, it will use hard float
(kernel should not use floating point) but the libgcc linked will be different too
and that should be OK ?
I've rewritten the changelog.
kernel builds set their own default -mcpu for a given ISA build.
But that gets in the way of "custom" -mcpu flags from propagating
into kernel build.
This will also be used in next patches for HSDK-4xD board support which
uses a different -mcpu to effect dual issue scheduling.
next prev parent reply other threads:[~2020-05-29 20:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 11:55 [PATCH 0/3] ARC: [plat-hsdk-4xd] initial port for HSDK-4xD board Eugeniy Paltsev
2020-05-29 11:55 ` [PATCH 1/3] ARC: allow to overide default mcpu compiler flag Eugeniy Paltsev
2020-05-29 20:47 ` Vineet Gupta [this message]
2020-05-29 11:55 ` [PATCH private 1/3] ARC: allow to overwrite " Eugeniy Paltsev
2020-05-29 12:10 ` Eugeniy Paltsev
2020-05-29 11:55 ` [PATCH 2/3] ARC: ARCv2: support loop buffer (LPB) disabling Eugeniy Paltsev
2020-05-29 20:47 ` Vineet Gupta
2020-05-29 11:55 ` [PATCH 3/3] ARC: [plat-hsdk-4xd] initial port for HSDK-4xD board Eugeniy Paltsev
2020-05-29 21:12 ` Vineet Gupta
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=c1dee77e-f8e3-1213-61a9-390412bfb5ee@synopsys.com \
--to=vineet.gupta1@synopsys.com \
--cc=Alexey.Brodkin@synopsys.com \
--cc=Eugeniy.Paltsev@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).