DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=JqZEWfZIhIzTzZYpZbskF7fV3gxdQ2tRjdVX3Mwiv3r
	bAXajYh4BjQOCNh1jJoxzz2m9v+O6FQCGAFpzpOU2Qne7Exr+ExWYiKPP/GfoOXF
	oXRIyfSrLphgjUHtExWy/b5vtiehHsaa85/0wMHWpGQTSkMCeHcI6VoA1PuelePs
	=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Message-ID: <52FBB0F8.80606@molconn.com>
Date: Wed, 12 Feb 2014 12:35:52 -0500
From: LMH <lmh_users-groups AT molconn DOT com>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:26.0) Gecko/20100101 Firefox/26.0 SeaMonkey/2.23
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: g77 on cygwin64
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> <CAMCbSMoqb_TsY3BQSU-AwnCOuCYecwCw4YexBQuUhbAbpSNDQg AT mail DOT gmail DOT com> <52FB8E3C DOT 3030704 AT appstate DOT edu> <52FBAC0B DOT 8000106 AT gmail DOT com>
In-Reply-To: <52FBAC0B.8000106@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


Marco Atzeri wrote:
> On 12/02/2014 16:07, Scott T. Marshall wrote:
>> Thank-you to those that responded with suggestions involving my fortran
>> issues. Fixing the code is not something I am going to pursue since the
>> source code was written by several different colleagues and is spread
>> out amongst many .f files. My colleagues have no interest in fixing it
>> since they have g77 on their unix machines, and to them, it isn't
>> broken. 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. So it is not clear to me exactly what
>> needs to be updated in the code.
>> I have tried to compile gcc 3.4.6 from source with no luck, but I am not
>> so good with compiler flags and makefiles. I will give it a go again,
>> but I am not optimistic.
>> So, to avoid further mean comments about my course of action being
>> "stupid", I will sign off.
>> -Scott
>>
>
> Hi Scott
>
> As he wrote "Sorry for my terrible english...",
> I assume it was not intentional offensive.
>
> Coming back to your issue, it is really curious that gfortran compiles
> the code but behaves wrongly, I was expecting it rejects the code
> if not in line with latest standard.
> I saw rejected code with lapack some time ago, and the correction was
> trivial. But compiling and not working is a serious gfortran bug.
>
> Have you a "short test case" ?
>
> Regards
> Marco
>
>
>
> --
> 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
>
>


 > Coming back to your issue, it is really curious that gfortran compiles
 > the code but behaves wrongly, I was expecting it rejects the code
 > if not in line with latest standard.

This happens on some of my code as well and is in many ways a far worse 
issue to deal with. Some of my code compiles and runs, but the floating 
point answers to many of the calculations are wrong. This makes the 
issue(s) very difficult to run down (and also makes me stick with gcc3 
like the posters colleagues).

LMH


--
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