X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:date:message-id:references :mime-version:content-type; q=dns; s=default; b=Dh1EEvo3AexZP2Jo M3awcE7Sfiq4ErDUzcRY6lg3oUIPkh44sFGeVaW+HVL1bOWT4M2perRfkLybeqTL n001Tj8tCaRyY9ztdeoskBKxn4ka7+0NDSGpz1BmdiPykv3mKEhpmYUmx4wiiyX4 i7NL8ra0Zoqpn8kM9iQC9cKwNFY= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:to:from:subject:date:message-id:references :mime-version:content-type; s=default; bh=rDrAxXy3WZ3iA1sG7F1646 uY9QY=; b=SKEimv5K7whI6zsuAPozcOP7m0iXiqERVJKPH167j0ZvAkaR8AMyTM CJJRIPLKPx/WUKCfx4KL28qZk4l++nP1WjHClKQIOiYtC5vo9Xcq9UlfUMnRRevl KQVD3Ap4cjNiSTs1Kp4GDeC2ey6k1HN+AvDOKrNBKnuf4vt4JI9Pw= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: plane.gmane.org To: cygwin AT cygwin DOT com From: Achim Gratz Subject: Re: g77 on cygwin64 Date: Wed, 12 Feb 2014 20:38:13 +0100 Lines: 27 Message-ID: <878utgjf4q.fsf@Rainer.invalid> References: <52FAF082 DOT 6020805 AT appstate DOT edu> <52FB0686 DOT 8080403 AT gmail DOT com> <52FB13E2 DOT 1070107 AT appstate DOT edu> <724410821 DOT 20140212111451 AT mtu-net DOT ru> <52FB8E3C DOT 3030704 AT appstate DOT edu> Mime-Version: 1.0 Content-Type: text/plain User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-IsSubscribed: yes Scott T. Marshall writes: > The strange thing is that gfortran does compile the > code, but once compiled, the executables have strange behavior mainly > involving problems reading in data files. To me this rather indicates a bug in the code, probably involving bad assumptions about what can be be done to files and in which order. For starters you might check if the files are opened in binary mode. > So it is not clear to me > exactly what needs to be updated in the code. Big can of worms. I've seen old Fortran code break on seemingly unrelated things like a C library security update, not to say what happened when I first tried to run it on an Alpha. You might try if the program works correctly if compiled unoptimized. Another option is to purposefully use a compiler that does things in a very different way and see where it complains and/or breaks (I've been keeping f2c for that). Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ SD adaptation for Waldorf microQ V2.22R2: http://Synth.Stromeko.net/Downloads.html#WaldorfSDada -- 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