delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-0.4 required=5.0 tests=AWL,BAYES_50,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RFC_ABUSE_POST,T_RP_MATCHES_RCVD,T_TO_NO_BRKTS_FREEMAIL |
X-Spam-Check-By: | sourceware.org |
Message-ID: | <4D74E275.9020902@aol.com> |
Date: | Mon, 07 Mar 2011 05:49:41 -0800 |
From: | Tim Prince <n8tm AT aol DOT com> |
User-Agent: | Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 |
MIME-Version: | 1.0 |
To: | cygwin AT cygwin DOT com |
Subject: | Re: 1.7.8: Fortran I/O rounding inaccuracy |
References: | <AANLkTinfV_nNY4kyR-rfxH8FKhKuwYSKt57qB=SZWbfa AT mail DOT gmail DOT com> |
In-Reply-To: | <AANLkTinfV_nNY4kyR-rfxH8FKhKuwYSKt57qB=SZWbfa@mail.gmail.com> |
x-aol-global-disposition: | G |
X-AOL-SCOLL-SCORE: | 0:2:357588224:93952408 |
X-AOL-SCOLL-URL_COUNT: | 0 |
x-aol-sid: | 3039ac1d33c44d74e277246c |
X-AOL-IP: | 99.13.231.72 |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
On 3/7/2011 4:17 AM, Thomas Henlich wrote: >> I doubt our compiler is Fortran 2008 compliant, as at maximum it will >> be Fortran 2003 > > An identical phrase appears in Fortran 2003. > >> Have you tested gfortran 4.3 on other platform ? > > Due to unavailability, I was not able to test this particular version > on other platforms. > > Tested ok: > > gfortran 4.4 on Debian > gfortran snapshot 20101129 on mingw32 > > Bug confirmed: > > gfortran snapshot 20100408 (unofficial Cygwin build) > You haven't shown how you tested rounding modes UP or DOWN, which may not be implemented in gfortran, as those (I believe) require the IEEE_arithmetic module, which is still under development. Doesn't the wording you quote apply to the binary value resulting from READ conversion? In the default (without IEEE_arithmetic settings), it's not clear to me that f2003 or 2008 standards impose requirements beyond those of IEEE754, which allow the decimal representation to truncate after 17 correct digits. As Corinna said, the place to ask about progress in this area of gfortran is fortran AT gcc DOT org. Corinna is more of an expert on newlib than are we; the differences you quote between linux implementation on glibc and cygwin which you quote appear to be within newlib. -- Tim Prince -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |