Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Phil Blundell" <pb@pbcl.net>
To: Khem Raj <raj.khem@gmail.com>
Cc: Andrea Adami <andrea.adami@gmail.com>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] RFC: pulseaudio vs. meson vs. neon
Date: Mon, 28 Jun 2021 23:21:07 +0200	[thread overview]
Message-ID: <20210628212107.GH5525@pbcl.net> (raw)
In-Reply-To: <f66a6a00-1a98-f8dd-e5d0-2c445147d5a7@gmail.com>

On Mon, Jun 28, 2021 at 02:10:39PM -0700, Khem Raj wrote:
> well, if we can beat the compiler to not complain about using neon on a
> non-neon system then yes, but changing float ABI to make compiler happy
> seems a bit iffy, since compiler will generate code expecting VFP and that
> could trip the system.

Right, that's a separate issue.  I'm not 100% clear what you mean by "trip
the system" but I think it's probably reasonable to say that no ABI ought
to be changing here.  I think that's orthogonal, though, to the question of
whether Meson ought to be detecting NEON at compile time.

p.


  reply	other threads:[~2021-06-28 21:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-28 10:01 RFC: pulseaudio vs. meson vs. neon Andrea Adami
2021-06-28 10:59 ` [OE-core] " Alexander Kanavin
2021-06-28 12:08   ` Andrea Adami
2021-06-28 12:36     ` Alexander Kanavin
2021-06-28 12:44       ` Andrea Adami
2021-06-28 13:03         ` Richard Purdie
2021-06-28 13:10           ` Andrea Adami
2021-06-28 17:55 ` Khem Raj
2021-06-28 18:20   ` Andrea Adami
2021-06-28 18:46     ` Khem Raj
2021-06-28 19:10       ` Phil Blundell
2021-06-28 19:42         ` Khem Raj
2021-06-28 19:52           ` Phil Blundell
2021-06-28 21:10             ` Khem Raj
2021-06-28 21:21               ` Phil Blundell [this message]
2021-06-28 21:40                 ` Khem Raj

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=20210628212107.GH5525@pbcl.net \
    --to=pb@pbcl.net \
    --cc=andrea.adami@gmail.com \
    --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