From: Adrian Bunk <bunk@stusta.de>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] tune-riscv: Add support for hard and soft float
Date: Sat, 9 Nov 2019 22:30:26 +0200 [thread overview]
Message-ID: <20191109203026.GA8956@localhost> (raw)
In-Reply-To: <023265d217840d956c5e54d12591d7cfdd0442b5.camel@linuxfoundation.org>
On Fri, Nov 08, 2019 at 11:07:04PM +0000, Richard Purdie wrote:
> On Fri, 2019-11-08 at 22:24 +0200, Adrian Bunk wrote:
> > Especially when looking at the arm64 situation I am wondering
> > whether the best option might be to throw away the tunes mess and let
> > the user write the compiler options directly.
>
> OE once did that. I think anyone who lived through it would say that
> the current situation *is* an improvement over a free-for-all.
>
> This is mainly as at least we're now consistent whereas before the same
> thing had different names in each BSP.
The BSPs should not invent names for anything, all a BSP should do would
be to set some kind of
TARGET_CFLAGS += "-mcpu=cortex-a53+crc+crypto+sm4+nosimd"
> I don't know what the answer is but I don't want to go back to that!
As of gcc 9 there are for arm64[1]:
6 -march= architecture levels (8.0 to 8.5)
35 -mtune= tune options
22 modifiers for -march= and -mtune=
3 different ABIs (aarch64, aarch64-ilp32, armv7)
Even ignoring the tunes you already have
6 * 2^22
different architecture+modifier combinations.
Not all combinations are valid, but another can of worms are the
definitions what is valid and what is default amd what gets indirectly
enabled, e.g.
fp16fml
Enable FP16 fmla extension. This also enables FP16 extensions and
floating-point instructions. This option is enabled by default for
-march=armv8.4-a. Use of this option with architectures prior to
Armv8.2-A is not supported.
It can be recursive:
Feature crypto implies aes, sha2, and simd, which implies fp.
Conversely, nofp implies nosimd, which implies nocrypto, noaes and nosha2.
> Cheers,
>
> Richard
cu
Adrian
[1] https://gcc.gnu.org/onlinedocs/gcc-9.1.0/gcc/AArch64-Options.html
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2019-11-09 20:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 18:18 [PATCH 1/2] tune-riscv: Add support for hard and soft float Alistair Francis
2019-11-06 18:18 ` [PATCH 2/2] arch-riscv: Default to hard float for riscv64 Alistair Francis
2019-11-06 20:54 ` [PATCH 1/2] tune-riscv: Add support for hard and soft float Khem Raj
2019-11-06 21:34 ` Alistair Francis
2019-11-06 21:49 ` Khem Raj
2019-11-06 21:52 ` Alistair Francis
2019-11-06 22:18 ` Khem Raj
2019-11-06 22:41 ` Alistair Francis
2019-11-06 22:12 ` Adrian Bunk
2019-11-06 22:43 ` Alistair Francis
2019-11-07 0:55 ` Khem Raj
2019-11-07 9:30 ` Adrian Bunk
2019-11-07 5:37 ` Nathan Rossi
2019-11-08 0:39 ` Alistair Francis
2019-11-08 20:24 ` Adrian Bunk
2019-11-08 23:07 ` Richard Purdie
2019-11-08 23:14 ` Alistair Francis
2019-11-12 0:21 ` Alistair Francis
2019-11-09 20:30 ` Adrian Bunk [this message]
2019-11-09 22:05 ` Richard Purdie
2019-11-10 16:08 ` Adrian Bunk
2019-11-13 8:48 ` Andre McCurdy
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=20191109203026.GA8956@localhost \
--to=bunk@stusta.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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