From: "Khem Raj" <raj.khem@gmail.com>
To: Phil Blundell <pb@pbcl.net>
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 14:10:39 -0700 [thread overview]
Message-ID: <f66a6a00-1a98-f8dd-e5d0-2c445147d5a7@gmail.com> (raw)
In-Reply-To: <20210628195238.GG5525@pbcl.net>
On 6/28/21 12:52 PM, Phil Blundell wrote:
> On Mon, Jun 28, 2021 at 12:42:55PM -0700, Khem Raj wrote:
>> On Mon, Jun 28, 2021 at 12:10 PM Phil Blundell <pb@pbcl.net> wrote:
>>>
>>> On Mon, Jun 28, 2021 at 11:46:08AM -0700, Khem Raj wrote:
>>>> I still hope that if we can add a proper neon detection patch to meson
>>>> they would be ok to accept it.
>>>
>>> Why doesn't the runtime detection work in the way that upstream clearly
>>> think it ought to?
>>
>> probably it does, someone has to test it on device without vfp.
>> Currently it is still failing to compile.
>> so first that needs to be fixed.
>
> Okay, but if the runtime detection does in fact work then there's no need
> for any NEON detection in Meson, right?
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.
>
> p.
>
next prev parent reply other threads:[~2021-06-28 21:10 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 [this message]
2021-06-28 21:21 ` Phil Blundell
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=f66a6a00-1a98-f8dd-e5d0-2c445147d5a7@gmail.com \
--to=raj.khem@gmail.com \
--cc=andrea.adami@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pb@pbcl.net \
/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