On Mon, May 18, 2020 at 9:56 PM Andrey Zhizhikin via lists.openembedded.org <[email protected]> wrote: > > On Thu, May 14, 2020 at 8:22 PM Khem Raj <[email protected]> wrote: > > > > > > > > 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. > > FYI: I've just seen this issue on the [optee-os] as well, build fails > with the same "undefined reference to `__getauxval'". Looks like it is > not only about valgrind... > > Any chance anyone had the same problem and proposed fix?
Actually, setting [-mno-outline-atomics] seems to help here, as Adrian suggested. I'll see if this could be used further as a fix. Sorry for the noise. > > > > > > The main effect in Yocto distributions is (slightly) slower and larger > > > code. > > > > > > cu > > > Adrian > > > > > > > > > -- > Regards, > Andrey. > -- Regards, Andrey.
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#138437): https://lists.openembedded.org/g/openembedded-core/message/138437 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]] -=-=-=-=-=-=-=-=-=-=-=-
