Re: f77 compiler
Dick Henry wrote: > In short, a program that works fine on my workstation gives different > output on my laptop using the f77 compiler from cygwin. Are you creating binary files? Just a wild guess (based on recently porting a Sun Fortran to cygwin), but then I'd assume you are running into big endian/little endian issues. Usually not a problem as long as you can recompile the program that uses the binary output under cygwin too. If thats not an option you'll need to do some data swabbing. Tony Richardson -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: f77 compiler
> -Original Message- > From: cygwin-owner On Behalf Of Dick Henry > Sent: 07 January 2005 17:16 > In short, a program that works fine on my workstation gives different > output on my laptop using the f77 compiler from cygwin. > I have no idea what's going on. Nor does anyone else. "Gives different output" is an entirely inadequate description of the problem. Are you doing floating point maths on systems with different accuracy in the underlying hardware? Is your code invoking undefined or unspecified behaviour that would differ from system to system? Do you place huge variables on the stack and are suffering from the two systems having different default stack sizes? There are a million possibilities why the same code might produce different output when compiled and run on two different machines, but most of them are down to buggy code rather than buggy compilers. >From a compiling standpoint, are there > other qualifiers that I should be using? You mean, is there some secret flag such as "-fwork-correctly", without which the cygwin f77 is deliberately supposed to produce garbage output? Heh, come on, is that even likely? "f77 --help -v >file.txt 2>&1" will produce a long file listing every single option the compiler (and the rest of the toolchain) knows; search it for "Options for Fortran" to find the fortran specific ones. But the problem is more likely in your code. cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
f77 compiler
Hi- I recently installed cygwin and have been testing various facets of it, namely the tasks that I usually perform on my sun workstation. All seems to work fine except I am having trouble with the fortran compiler. In short, a program that works fine on my workstation gives different output on my laptop using the f77 compiler from cygwin. The compiling command I am using on my laptop is: f77 -ffixed-line-length-none open.f -o open This compiles the program open.f and generates open.exe. I receive no error messages. Numerous lines in the program are longer than 80 spaces, hence the -ffixed--- qualifier. I have no idea what's going on. From a compiling standpoint, are there other qualifiers that I should be using? FYI, on my workstation I compile using: f77 -e open.f -o open Thanks very much. Dick Henry U. of Oklahoma ** Richard C. Henry Department of Physics & Astronomy University of Oklahoma Norman, OK 73019 USA phone: 405-325-3961 x36221 fax: 405-325-7557 email: [EMAIL PROTECTED] ** -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
