On Wed, 20 Sep 2017, Martin Sebor wrote: > I'm not intimately familiar with the Glibc ifunc infrastructure > to suggest a good solution here, so assuming this works my only > idea is to suppress the warning for these builds. > > Joseph, do you have a better suggestion?
Is the warning because of a declaration of memmove as aliasing __libc_memmove being compared with the type of the __libc_memmove_ifunc declaration (asm name __libc_memmove) rather than the __libc_memmove declaration? If so, maybe in the non-HAVE_GCC_IFUNC case the alias should be declared with a different type? Or should be defined inside asm in this case (presumably with new ifunc-related macros)? (It may nevertheless be a good idea to set default_gnu_indirect_function=yes for AArch64 configurations in GCC that use glibc.) -- Joseph S. Myers jos...@codesourcery.com
