Mark Dickinson <[EMAIL PROTECTED]> added the comment:
On Mon, Jun 23, 2008 at 5:25 PM, Jean Brouwers <[EMAIL PROTECTED]>
wrote:
> result is different for 32- and 64-bit
>
> > cc -xtarget=native log_inf.c -lm ; a.out
> -Inf 33
> Inf 33
>
That 33 for the second log call may just be the propagated errno value
from the first call. Could you try setting errno = 0 before each of the
printf
calls? I'd expect that log(HUGE_VAL) doesn't set errno at all.
Mark
Added file: http://bugs.python.org/file10722/unnamed
_______________________________________
Python tracker <[EMAIL PROTECTED]>
<http://bugs.python.org/issue3167>
_______________________________________
<div class="gmail_quote">On Mon, Jun 23, 2008 at 5:25 PM, Jean Brouwers <<a
href="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]</a>> wrote:<br><blockquote
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex;">
<div class="Ih2E3d">result is different for 32- and 64-bit<br></div>
<br>
> cc -xtarget=native log_inf.c -lm ; a.out<br>
-Inf 33<br>
Inf 33<br></blockquote><div><br></div><div>That 33 for the second log call may
just be the propagated errno value</div><div>from the first call. Could
you try setting errno = 0 before each of the printf</div><div>calls?
I'd expect that log(HUGE_VAL) doesn't set errno at all.</div>
<div><br></div><div>Mark</div></div>
_______________________________________________
Python-bugs-list mailing list
Unsubscribe:
http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com