From 092a7a80fd95b6f347b53779066af3319d3669f8 Mon Sep 17 00:00:00 2001 From: Tim Peters Date: Mon, 1 Oct 2001 19:50:06 +0000 Subject: [PATCH] SF patch [#466353] Py_HUGE_VAL on BeOS for Intel. The patch repaired internal gcc compiler errors on BeOS. This checkin repairs them in a simpler way, by explicitly casting the platform INFINITY to double. --- Include/pyport.h | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/Include/pyport.h b/Include/pyport.h index 15a480a8bbea..5f8ccf7c132d 100644 --- a/Include/pyport.h +++ b/Include/pyport.h @@ -235,9 +235,13 @@ extern "C" { * on some Cray systems HUGE_VAL is incorrectly (according to the C std) * defined to be the largest positive finite rather than infinity. We need * the std-conforming infinity meaning (provided the platform has one!). + * + * Then, according to a bug report on SourceForge, defining Py_HUGE_VAL as + * INFINITY caused internal compiler errors under BeOS using some version + * of gcc. Explicitly casting INFINITY to double made that problem go away. */ #ifdef INFINITY -#define Py_HUGE_VAL INFINITY +#define Py_HUGE_VAL ((double)INFINITY) #else #define Py_HUGE_VAL HUGE_VAL #endif