On Fri, Sep 16, 2011 at 08:41:47PM +0200, Martin Husemann wrote: > On Fri, Sep 16, 2011 at 09:16:23PM +0300, Jukka Ruohonen wrote: > > Is there any consistent way to know which functions are available on VAX? > > Or even more generally, any consistent way to know which libm(3) functions > > are available on which architectures? (That is, there are ugly hacks like > > "#ifdef i386 || sparc || amd64" too.) > > Good question. I consider all those as "hacks", they should be documented > and fixed, the soone the better. > > Or, if there are hidden reasons, we should document them better and rename > the ifdefs to some __HAVE_... feature tests. > > For VAX it is pretty easy: there is no NAN nor +/-INF (and IIRC zero is > zero, no +/- zero). Everything else is a bug somewhere and fixable.
The other things I can think of are: - Denormalised values near zero (normally true) - Strange byte orderings. David -- David Laight: da...@l8s.co.uk