From: "Adrian Bunk" <bunk@stusta.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH V3 3/3] gcc10: Revert using __getauxval in libgcc
Date: Thu, 14 May 2020 18:29:34 +0300 [thread overview]
Message-ID: <20200514152934.GC21399@localhost> (raw)
In-Reply-To: <20200511182812.441561-3-raj.khem@gmail.com>
Disabling -moutline-atomics would also workaround this issue.
And I think it would be the right thing to do for Yocto in any case.
-moutline-atomics makes sense for binary distributions that want to
offer both high performance for heavily threaded code on >= ARMv8.1
and support ARMv8.0 in the same binaries.
I do not see usecases for this in Yocto that would justify
the small performance penalty from -moutline-atomics.
cu
Adrian
next prev parent reply other threads:[~2020-05-14 15:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 18:28 [PATCH V3 1/3] gcc10: Update to GCC 10.1 Release Khem Raj
2020-05-11 18:28 ` [PATCH V3 2/3] gcc10: Default back to -fcommon Khem Raj
2020-05-12 13:44 ` [OE-core] " Adrian Bunk
2020-05-12 15:16 ` Khem Raj
2020-05-12 15:40 ` Adrian Bunk
2020-05-12 15:54 ` Khem Raj
2020-05-11 18:28 ` [PATCH V3 3/3] gcc10: Revert using __getauxval in libgcc Khem Raj
2020-05-14 7:38 ` [OE-core] " Adrian Bunk
2020-05-14 12:47 ` Khem Raj
2020-05-14 13:16 ` Adrian Bunk
2020-05-14 13:56 ` Khem Raj
2020-05-14 14:07 ` Adrian Bunk
2020-05-14 14:48 ` Khem Raj
2020-05-14 15:18 ` Adrian Bunk
2020-05-14 15:29 ` Adrian Bunk [this message]
2020-05-14 17:18 ` Khem Raj
2020-05-14 18:19 ` Adrian Bunk
2020-05-14 18:22 ` Khem Raj
2020-05-18 19:56 ` Andrey Zhizhikin
[not found] ` <16103797E38CE61D.31744@lists.openembedded.org>
2020-05-18 21:20 ` Andrey Zhizhikin
2020-05-12 5:45 ` [OE-core] [PATCH V3 1/3] gcc10: Update to GCC 10.1 Release Jacob Kroon
2020-06-17 6:59 ` kai
2020-06-17 15:50 ` Khem Raj
2020-06-19 3:17 ` kai
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=20200514152934.GC21399@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