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:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; q=dns; s=default; b=F4 fbPXoifR0wi1SNuYZzSfrKTPmxmMaTyI2Gzxl6mHGpKmj6aMx6iOT04s/NQqbsRU R4inR89qCIfTmyE4WsB6vQZImzqQkYRJu8/6LLys79lbI9PDhP6BVmRpFVhDkkTO ZVbdJ+up+6eUhc7KFEGNILa3D1ISU+hxEsS9Yt4bs= 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:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; s=default; bh=ybDAGoR4 wsGGgKlfu23jE1oxU04=; b=IYYjqpFG+QoJDaMDfMgf6YP+yTBJoZlJEU+8p1to cVJyt2xHuKCTMHtcuofmFp8fULauiqt5PM6s8oqhViXQlnJa6o3KS6c9iLjbm0bO 21F2yTgzJQxpin1aUI0nhH3o+nDVbE897Q4PoF+1FElKGbORqJ2TOq0Asxb1YlO+ Tbc= 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.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-la0-f50.google.com MIME-Version: 1.0 X-Received: by 10.112.163.167 with SMTP id yj7mr54794lbb.88.1392227987259; Wed, 12 Feb 2014 09:59:47 -0800 (PST) In-Reply-To: <1436686110.20140212211626@mtu-net.ru> 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> <1436686110 DOT 20140212211626 AT mtu-net DOT ru> Date: Wed, 12 Feb 2014 12:59:47 -0500 Message-ID: Subject: Re: g77 on cygwin64 From: David Conrad To: Andrey Repin Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes On Wed, Feb 12, 2014 at 12:16 PM, Andrey Repin wrote: >> 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. ... > > And this is finally the information, that we can work with. > My wild guess is that your "colleagues" making certain assumptions about > files, that not always true on other systems. > I.e. opening a file in text mode, and then treating [its] data as binary ... Since the problem occurs going from 32-bit to 64-bit Cygwin, it sounds to me like all-the-world's-a-VAX syndrome. I bet there are places where it reads from files and assumes that if it reads N words into integers, that is N 32-bit quantities, or something like that. I haven't written any Fortran since the 1980s, but I bet there are types that have changed size due to the switch to 64-bit and that results in reading incorrect values from files, including reading some of them from the wrong file offsets, and hitting end-of-file at a different point. Are there any switches to gfortran that control this? I took a brief look, and the only thing I saw was the -finteger-4-integer-8 option and friends, but that sounds like going the opposite direction you want to go, and the -ff2c option that generates C code. You could run the code through g77 on 32-bit, gfortran on 64-bit, and compare the C code generated for the file handling. But I suspect that's more hassle than you want to get into; it doesn't sound like fun to me. Good luck. -- 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