This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH, i386]: Handle IX86_BUILTIN_INFQ and IX86_BUILTIN_HUGE_VALQ in ix86_fold_builtin


On Thu, Oct 20, 2016 at 11:33:14PM +0000, Joseph Myers wrote:
> On Fri, 21 Oct 2016, Uros Bizjak wrote:
> 
> > 2016-10-21  Uros Bizjak  <ubizjak@gmail.com>
> > 
> >     * config/i386/i386.c (ix86_fold_builtin): Handle IX86_BUILTIN_INFQ
> >     and IX86_BUILTIN_HUGE_VALQ here ...
> >     (ix86_expand_builtin): ... not here.
> > 
> > Bootstrapped and regression tested on x86_64-linux-gnu {,-m32}.
> > Committed to mainline SVN.
> 
> Do you know if it's possible to make architecture-specific built-in 
> functions into aliases of architecture-independent ones?  That would be 
> the ideal thing for the *q __float128 functions - make them aliases of the 
> *f128 architecture-independent ones, and so subject to any 
> architecture-independent optimizations (for these two there's nothing more 
> than folding to do, but at some point I expect we'll optimize fabsf128 and 
> copysignf128 as much as the corresponding functions for float / double / 
> long double, for example).

I guess e.g. ix86_fold_builtin could just fold those builtins into calls to
the arch-indepdendent ones, so while it wouldn't be an alias, it could be
represented as the arch-independent builtin from gimplification onwards.

	Jakub


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]