On Wed, Oct 11, 2023 at 10:59:10AM +0200, Florian Weimer wrote: > * Andrew Carlotti via Gcc: > > > I've also seen the GCC documentation for the ifunc attribute [1]. > > This states that "the indirect function needs to be defined in the > > same translation unit as the resolver function". This is not how > > function multiversioning is currently implemented. Instead, the > > resolver functions are added to the translation units of every caller. > > I don't see how this can happen. Do you have a declaration of the > resolver function in a shared header, by chance? > > Thanks, > Florian
I haven't explicity declared a separate function. I just included the normal function multiversioning attributes on the function declarations. If you don't include the attributes on the declarations, then you will get one of two issues: - For target_clones, you would need to ensure that the mutiversioned function has a caller in the same translation unit as the implementations. If you don't do this, then no resolver will be generated, with all of the callers referencing a non-existent symbol. - For target versions, any caller that cannot see the function multiversioning attributes will only ever use the default version of the function. This also applies to the current aarch64 specification for target_clones and target_version.
