automatically updating ulps -- any review needed ?

[Mike Frysinger]

the ia64 code hasn't had its ulps file regenerated in a long time.  i used the 
helper target for regenerating things, and now i'm looking at the diff.  but i 
have no idea how to evaluate what these differences mean :).  most are easy -- 
new baselines for tests that didn't have any info recorded previously.

i tried reading math/README.libm-test, but it seems like some base knowledge 
is assumed.

for example, i don't know what to make of things like:
 Function: "yn":
 double: 3
-float: 2
+float: 3
 idouble: 3
-ifloat: 2
+ifloat: 3
 ildouble: 2
 ldouble: 2

or am i thinking too hard about this and i should just commit it and forget ?
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20140105/0545b687/attachment.sig>