From: "Adrian Bunk" <bunk@stusta.de>
To: Andre McCurdy <armccurdy@gmail.com>
Cc: Stefan Ghinea <stefan.ghinea@windriver.com>,
OE Core mailing list <openembedded-core@lists.openembedded.org>
Subject: Re: [OE-core] [PATCH] pulseaudio: fix for ARM thumb + frame pointers compilation error
Date: Fri, 27 Mar 2020 20:56:16 +0200 [thread overview]
Message-ID: <20200327185616.GB23840@localhost> (raw)
In-Reply-To: <CAJ86T=ULPheVBCFMQd8-rF5v6YyCpO6phPZqeYW88NtL=f=t+g@mail.gmail.com>
On Thu, Mar 26, 2020 at 02:23:03PM -0700, Andre McCurdy wrote:
>...
> Right, it's not related to musl or glibc. I suspect it can be
> reproduced by building for an ARM target which supports NEON, ensuring
> that DEFAULTTUNE doesn't forcefully disable Thumb (e.g. it should be
> armv7vethf-neon, not armv7vehf-neon), setting ARM_INSTRUCTION_SET to
> thumb and then compiling with frame pointers enabled (e.g. by adding
> -fno-omit-frame-pointer to CFLAGS).
>...
Thanks, this was helpful in figuring out what I missed when testing.
I can now confirm that the problem still exists, also with glibc.
cu
Adrian
next prev parent reply other threads:[~2020-03-27 18:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 15:26 [PATCH] pulseaudio: fix for ARM thumb + frame pointers compilation error Stefan Ghinea
2020-03-26 17:23 ` [OE-core] " Andre McCurdy
2020-03-26 19:16 ` Adrian Bunk
2020-03-26 19:53 ` Andre McCurdy
2020-03-26 20:26 ` Adrian Bunk
2020-03-26 21:23 ` Andre McCurdy
2020-03-27 18:56 ` Adrian Bunk [this message]
2020-07-17 10:09 ` Tanu Kaskinen
2020-07-17 19:19 ` Andre McCurdy
2020-07-18 4:09 ` Tanu Kaskinen
2020-03-30 16:29 ` Tanu Kaskinen
[not found] ` <160121D94406B75D.27565@lists.openembedded.org>
2020-03-30 16:52 ` Tanu Kaskinen
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=20200327185616.GB23840@localhost \
--to=bunk@stusta.de \
--cc=armccurdy@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=stefan.ghinea@windriver.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