[Bug fortran/98701] I compiled a program with gfortran on Mac (Big Sur, version 11.1) and g77 on Windows 10. I get two very different results for identical input files with the results from the one c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 --- Comment #16 from Bahram.shahrooz at uc dot edu --- I spent a good chunk of today to debug. The culprit was two variables that had not been set equal to 0. I get the same results with g77 on Windows, GFortran on Mac Big Sur, & AbsoftTools ( I

[Bug fortran/98701] I compiled a program with gfortran on Mac (Big Sur, version 11.1) and g77 on Windows 10. I get two very different results for identical input files with the results from the one c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 --- Comment #13 from Bahram.shahrooz at uc dot edu --- Thank you for your help. I really appreciate your time.

[Bug fortran/98701] I compiled a program with gfortran on Mac (Big Sur, version 11.1) and g77 on Windows 10. I get two very different results for identical input files with the results from the one c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 --- Comment #11 from Bahram.shahrooz at uc dot edu --- Thanks! This is how I compiled: gfortran FiberAnalysis.f -finit-real=nan -fcheck=all -ffpe-trap=zero,invalid -o FiberAnalysis_v2 This what I get after running (the answers are correct): P

[Bug fortran/98701] I compiled a program with gfortran on Mac (Big Sur, version 11.1) and g77 on Windows 10. I get two very different results for identical input files with the results from the one c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 --- Comment #9 from Bahram.shahrooz at uc dot edu --- Yes, thank you for finding this bug. Things didn't change after changing estart to estrt. Sorry, I don't know how to use -freal-init=nan. I tried to use it like this but got an error. % gfo

[Bug fortran/98701] I compiled a program with gfortran on Mac (Big Sur, version 11.1) and g77 on Windows 10. I get two very different results for identical input files with the results from the one c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 --- Comment #6 from Bahram.shahrooz at uc dot edu --- I get wrong answers doing this: gfortran FiberAnalysis.f -o FiberAnalysis I get correct answers doing this: gfortran FiberAnalysis.f -fcheck=all -ffpe-trap=zero,invalid -o FiberAnalysis

[Bug fortran/98701] I compiled a program with gfortran on Mac (Big Sur, version 11.1) and g77 on Windows 10. I get two very different results for identical input files with the results from the one c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 --- Comment #4 from Bahram.shahrooz at uc dot edu --- I compiled with the suggested options (below) and now the code gives the same result as g77. -fcheck=all -ffpe-trap=zero,invalid Things look good now! Sorry for starting this bug report prem

[Bug fortran/98701] I compiled a program with gfortran on Mac (Big Sur, version 11.1) and g77 on Windows 10. I get two very different results for identical input files with the results from the one c

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 --- Comment #3 from Bahram.shahrooz at uc dot edu --- Created attachment 49979 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49979&action=edit source code Sorry, I had to zip several files. Readme file in Archive.zip explains what the file

[Bug fortran/98701] New: I compiled a program with gfortran on Mac (Big Sur, version 11.1) and g77 on Windows 10. I get two very different results for identical input files with the results from the

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98701 Bug ID: 98701 Summary: I compiled a program with gfortran on Mac (Big Sur, version 11.1) and g77 on Windows 10. I get two very different results for identical input files with the