On 2/12/2014 9:07 AM, Scott T. Marshall wrote:
My colleagues have no interest in fixing it since they have g77 on their
unix machines, and to them, it isn't broken.
Perhaps your colleagues would be willing to look at your results and
tell you whether there is a trivial fix for your problem. g
On 2/12/2014 12:59 PM, David Conrad wrote:
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 infor
On 12/02/2014 20:06, Richard wrote:
Yeah, I was there, fought those battles. The proof of what was going on
was found in crash dumps. ...This was from the era when "RISC
architecture" meant "Relegate all the Important Sh_t to the Compiler."
Richard
More recently, all wchar_t are 4 byte l
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
On 12/02/2014 18:35, LMH wrote:
> 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
i
On Wed, 12 Feb 2014, David Conrad wrote:
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 somethi
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
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 ma
Greetings, Scott T. Marshall!
Please don't http://cygwin.com/acronyms/#TOFU
> 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
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 colleag
On Wed, Feb 12, 2014 at 11:14:51AM +0400, Andrey Repin wrote:
>Greetings, Scott T. Marshall!
>> Would it be very difficult to take the old g77 source and recompile it
>> for cygwin64? Has anyone successfully done this before?
>
>It would certainly be easier to fix you code to compile with
>standard
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
I agree with Andrey - could you give us examples of code fragments
that are not accepted by gfortran but are by g77?
Regards,
Arjen
2014-02-12 8:14 GMT+01:00 Andrey Repin :
> Greetings, Scott T. Marshall!
>
>> Would it be very difficult to take the old g77 source and recompile it
>> for cygwin64
What host operating system are you running cygwin on? Do you have
examples of your old g77 applications that are already compiled that you
can test on your current system?
There are several options. Compiling g77 is one of them, but you would
need the proper runtime components as well. It is a
Greetings, Scott T. Marshall!
> Would it be very difficult to take the old g77 source and recompile it
> for cygwin64? Has anyone successfully done this before?
It would certainly be easier to fix you code to compile with
standards-conformant compiler.
Because every other course of action seems c
On 2/12/2014 12:28 AM, Marco Atzeri wrote:
On 12/02/2014 04:54, Scott T. Marshall wrote:
Hi All,
First a compliment: I recently went from the old x86 version of cygwin
to cygwin64. I was pleased to see that many of my perl scripts run about
twice as fast. Thanks!
My question: Would it be pos
On 12/02/2014 04:54, Scott T. Marshall wrote:
Hi All,
First a compliment: I recently went from the old x86 version of cygwin
to cygwin64. I was pleased to see that many of my perl scripts run about
twice as fast. Thanks!
My question: Would it be possible to have the old g77 fortran compiler
as
Hi All,
First a compliment: I recently went from the old x86 version of cygwin
to cygwin64. I was pleased to see that many of my perl scripts run about
twice as fast. Thanks!
My question: Would it be possible to have the old g77 fortran compiler
as an optional install for cygwin64? I realize
18 matches
Mail list logo
