This is the mail archive of the
mailing list for the GCC project.
Re: [RFC] Formation of vector function name
- From: Joseph Myers <joseph at codesourcery dot com>
- To: Andrew Pinski <pinskia at gmail dot com>
- Cc: Andrew Senkevich <andrew dot n dot senkevich at gmail dot com>, GCC Mailing List <gcc at gcc dot gnu dot org>
- Date: Tue, 16 Jun 2015 14:23:27 +0000
- Subject: Re: [RFC] Formation of vector function name
- Authentication-results: sourceware.org; auth=none
- References: <CAMXFM3t8McrwJk=MoKXmwXc=pOisaSS1MtLYOqBBiSaZfJpy2Q at mail dot gmail dot com> <CA+=Sn1k68D0N-Te26T7SF0zfOJUqm0A8WOTAqS-jrJmeTJ5p=Q at mail dot gmail dot com>
On Mon, 15 Jun 2015, Andrew Pinski wrote:
> > results in asm redirection for log to __log_finite and final vector
> > function name becomes _ZGVbN2v___log_finite.
> > With point of view from C Library side, it reflects in addition of asm
> > redirections _ZGVbN2v___log_finite = _ZGVbN2v_log in the headers.
> > May be the cleaner way is to base vector name on original name of
> > declaration, not asm declaration name (use DECL_NAME instead of
> > DECL_ASSEMBLER_NAME)?
> I don't think this would be useful really because if you have a
> function say logl where you have two options of long double, you want
> to support both you would name one logl and the other logl128 and then
> using DECL_ASSEMBLER_NAME to from the SIMD name would be useful to use
> the one with logl128 in it rather than logl.
The point is that the vector versions may not be in one-to-one
correspondence with the scalar versions - you might have several different
scalar versions depending on compiler options, all of which correspond to
a single vector version.
Joseph S. Myers