On 5/14/20 11:19 AM, Adrian Bunk wrote:
On Thu, May 14, 2020 at 10:18:53AM -0700, Khem Raj wrote:
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
...

Not just for valgrind, globally.


so far just doing for valgrind is enough. I am not averse to enabling it globally but perhaps we need to do some pre-work to decide that, maybe some benchmark numbers.

The main effect in Yocto distributions is (slightly) slower and larger code.

cu
Adrian

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#138287): 
https://lists.openembedded.org/g/openembedded-core/message/138287
Mute This Topic: https://lists.openembedded.org/mt/74142400/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to