All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alistair Francis <alistair23@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: OE-core <openembedded-core@lists.openembedded.org>,
	Adrian Bunk <bunk@stusta.de>
Subject: Re: [PATCH 1/2] tune-riscv: Add support for hard and soft float
Date: Fri, 8 Nov 2019 15:14:54 -0800	[thread overview]
Message-ID: <CAKmqyKNENL0De4uJqDDn-04-QZb2za6NXt2e+yU9fWZAY6jpMg@mail.gmail.com> (raw)
In-Reply-To: <023265d217840d956c5e54d12591d7cfdd0442b5.camel@linuxfoundation.org>

On Fri, Nov 8, 2019 at 3:07 PM Richard Purdie
<richard.purdie@linuxfoundation.org> 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.
>
> I don't know what the answer is but I don't want to go back to that!

Ha ok. I won't argue with that.

I can just carry the patch locally, so I'm not in a rush to get this
in. I have reached out to Rich (musl maintainer) to see if he has any
ideas.

Alistair

>
> Cheers,
>
> Richard
>
>
>


  reply	other threads:[~2019-11-08 23:15 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 [this message]
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=CAKmqyKNENL0De4uJqDDn-04-QZb2za6NXt2e+yU9fWZAY6jpMg@mail.gmail.com \
    --to=alistair23@gmail.com \
    --cc=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 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.