On Wed, 3 Aug 2016, Ramana Radhakrishnan wrote: > Joseph, do you have any opinions on whether we should be extending the > standard pattern names or not for btrunc, ceil, round, floor, > nearbyint, rint, lround, lfloor and lceil optabs for the HFmode > quantities ?
If the semantics match a standard pattern, you should use the standard name. It may well be the case that many of those patterns would not actually be used for generic code even after my _FloatN patches, since (a) I only add a minimal set of built-in functions, not the full set of all libm functions for all _FloatN / _FloatNx types (given possible issues with enum size and initialization time when seven new variants of every libm function are added as built-in functions) and (b) many relevant optimizations only work for float, double and long double. But I think the right pattern names should still be used. -- Joseph S. Myers [email protected]
