Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] tune-riscv: Add support for hard and soft float
Date: Thu, 7 Nov 2019 11:30:38 +0200	[thread overview]
Message-ID: <20191107093038.GA15395@localhost> (raw)
In-Reply-To: <CAMKF1soRzN+thjSsMsz2F0_cxTGkS+cpKAYwiAYs4d3YFhjh7g@mail.gmail.com>

On Wed, Nov 06, 2019 at 04:55:05PM -0800, Khem Raj wrote:
> On Wed, Nov 6, 2019 at 4:48 PM Alistair Francis <Alistair.Francis@wdc.com>
> wrote:
>...
> > -march is another can of worms that I was trying to avoid. I don't have
> > a good way of handling the ISA strings at the moment without some crazy
> > number of tune options.
> 
> We need to handle that but I think that should be in meta-riscv since I
> think for Linux we should just stick to rv64gc ABI and something cross
> distro agreed upon abi for riscv32 and bare metal is another story that’s
> where probably we need to address the ABIs

We have the same problem even worse on arm64,
with billions of combinations available.

A solution is needed in both cases.

cu
Adrian

-- 

       "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



  reply	other threads:[~2019-11-07  9: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 [this message]
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
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=20191107093038.GA15395@localhost \
    --to=bunk@stusta.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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