# Help me find this gfortran bug for ARM machines

**URL:** <https://fortran-lang.discourse.group/t/help-me-find-this-gfortran-bug-for-arm-machines/2611>\
**Category:** Help\
**Created:** [January 18, 2022, 5:25pm UTC](https://fortran-lang.discourse.group/t/help-me-find-this-gfortran-bug-for-arm-machines/2611 "2022-01-18T17:25:52Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![nicholaswogan](https://avatars.discourse-cdn.com/v4/letter/n/f1d935/32.png) [@nicholaswogan](https://fortran-lang.discourse.group/u/nicholaswogan)\
**Post date:** [January 19, 2022, 6:27am UTC](https://fortran-lang.discourse.group/t/help-me-find-this-gfortran-bug-for-arm-machines/2611/8 "2022-01-19T06:27:23Z")

</div>

@mecej4 thanks so much! This is really helpful. After fixing the `wa` variable, it works on my MacOS M1 machine. I should have written module interfaces for the old minpack routine. This bug would have been caught by the compiler if I had.

I was suspicious of compiler bug because I found one recently: [Why am I getting a segmentation fault here (M1 Mac)? - #3 by nicholaswogan](https://fortran-lang.discourse.group/t/why-am-i-getting-a-segmentation-fault-here-m1-mac/2437/3)

---

_[View the full topic](https://fortran-lang.discourse.group/t/help-me-find-this-gfortran-bug-for-arm-machines/2611)._