I’m running an older Fortran code on MacOS Big Sur with apple silicon. There is a compiler bug that I can not identify specifically. I’d like to find it, so I can make sure the GNU developers know about it. Here is the code: GitHub - Nicholaswogan/ImpactAtmosphere at dev compile with cmake in the …

Here are three errors that I found. There are three places in EvolveAtmFort.f90 where workspace arrays WA are allocated. Those should have been declared as type double precision, whereas you have declared them as type integer. As a consequence, the workspace passed in the second and third calls is s…

Help me find this gfortran bug for ARM machines

Help

certik Split this topic January 22, 2022, 3:56am 12

5 posts were split to a new topic: Moving minpack under fortran-lang

Topic		Replies	Views
Why a simple code, Intel Fortran -O3 -O2 gives wrong results? Help	17	1946	September 23, 2021
Why am I getting a segmentation fault here (M1 Mac)? Help	10	7005	December 22, 2021
Let's get LFortran to compile Minpack	8	2246	January 30, 2023
Does sometimes -O2, -O3, -Ofast flags cause segment 11 error on Mac M1 chip?	8	909	March 14, 2022
NAG® Fortran Compiler now fully supports Fortran 2008 and Coarray Fortran 2018 Announcements	17	1198	December 7, 2021

Help me find this gfortran bug for ARM machines

Related topics