From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1222 invoked by alias); 27 Jul 2007 05:56:37 -0000 Received: (qmail 1191 invoked by alias); 27 Jul 2007 05:56:27 -0000 Date: Fri, 27 Jul 2007 05:56:00 -0000 Message-ID: <20070727055627.1190.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libfortran/32841] [4.3 regression] HUGE(1.0d0) is written a +Infinity on Darwin8 In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "dominiq at lps dot ens dot fr" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2007-07/txt/msg02730.txt.bz2 ------- Comment #17 from dominiq at lps dot ens dot fr 2007-07-27 05:56 ------- Subject: Re: [4.3 regression] HUGE(1.0d0) is written a +Infinity on Darwin8 > Maybe you could try to delete the conditional defines that redefine isfinite so > that the native calls are used and see if the problem goes away. I have done something slightly different, but with the same result, I have moved line 167: #undef isfinite outside the #if defined(HAVE_BROKEN_ISFINITE) || defined(__CYGWIN__) block. This change fixes the bug, edit_real_1.f90 pass. Now the questions are (1) why HAVE_BROKEN_ISFINITE is not set by gcc 4.3 while it is by gcc 4.2? (2) if the isfinite used by C is working, why isfinite is not working for libfortran? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32841