On 5/14/20 8:29 AM, Adrian Bunk wrote:
Disabling -moutline-atomics would also workaround this issue.
I think this is a good suggestion and I do not like to revert gcc patches if we can avoid doing that. I will propose a fix to disable outline-atomics for valgrind on aarch64
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
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#138278): https://lists.openembedded.org/g/openembedded-core/message/138278 Mute This Topic: https://lists.openembedded.org/mt/74142400/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
