[Bug fortran/100183] Segmentation fault at runtime when passing an internal procedure as argument
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100183 Andrew Pinski changed: What|Removed |Added Resolution|--- |MOVED Status|NEW |RESOLVED --- Comment #7 from Andrew Pinski --- Yes this was a the nested functions being passed to another function issue where executable stack was needed for aarch64-darwin, there is no executable stack. Anyways this was tracked as https://github.com/iains/gcc-darwin-arm64/issues/26 and was just fixed so closing as moved as aarch64-darwin is not supported yet in the FSF sources (Ians and FX are planning on merging it upstream sometime this year).
[Bug fortran/100183] Segmentation fault at runtime when passing an internal procedure as argument
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100183 Andrew Pinski changed: What|Removed |Added Status|WAITING |NEW See Also||https://github.com/iains/gc ||c-darwin-arm64/issues/26
[Bug fortran/100183] Segmentation fault at runtime when passing an internal procedure as argument
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100183 --- Comment #6 from Iain Sandoe --- (In reply to anlauf from comment #5) > (In reply to Iain Sandoe from comment #4) > > gcc304 is the Apple M1 machine. The GCC support there is highly > > experimental and not in master -- please note that there are known issues > > with the implementation. > > > > see : https://github.com/iains/gcc-darwin-arm64/issues > > So rather a target than a fortran issue? The fortran folks have fixed a number of cases recently where the FE was providing bad information to the ME .. which doesn't cause problems to most targets, but did to aarch64-darwin. I cannot rule out that this is another case in that category (but not had a chance to analyse it yet).
[Bug fortran/100183] Segmentation fault at runtime when passing an internal procedure as argument
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100183 anlauf at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |WAITING Ever confirmed|0 |1 Last reconfirmed||2021-04-29 --- Comment #5 from anlauf at gcc dot gnu.org --- (In reply to Iain Sandoe from comment #4) > gcc304 is the Apple M1 machine. The GCC support there is highly > experimental and not in master -- please note that there are known issues > with the implementation. > > see : https://github.com/iains/gcc-darwin-arm64/issues So rather a target than a fortran issue?
[Bug fortran/100183] Segmentation fault at runtime when passing an internal procedure as argument
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100183 --- Comment #4 from Iain Sandoe --- (In reply to Ignacio Fernández Galván from comment #3) > If it helps, this happens in gcc304 from > https://cfarm.tetaneutral.net/machines/list/, but not in gcc80 gcc304 is the Apple M1 machine. The GCC support there is highly experimental and not in master -- please note that there are known issues with the implementation. see : https://github.com/iains/gcc-darwin-arm64/issues
[Bug fortran/100183] Segmentation fault at runtime when passing an internal procedure as argument
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100183 --- Comment #3 from Ignacio Fernández Galván --- If it helps, this happens in gcc304 from https://cfarm.tetaneutral.net/machines/list/, but not in gcc80
[Bug fortran/100183] Segmentation fault at runtime when passing an internal procedure as argument
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100183 Richard Biener changed: What|Removed |Added CC||iains at gcc dot gnu.org Target||aarch64-darwin --- Comment #2 from Richard Biener --- Cannot reproduce on x86_64.
[Bug fortran/100183] Segmentation fault at runtime when passing an internal procedure as argument
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100183 --- Comment #1 from anlauf at gcc dot gnu.org --- Cannot reproduce either with GNU Fortran (SUSE Linux) 10.2.1 20200825 [revision c0746a1beb1ba073c7981eb09f55b3d993b32e5c] nor with GNU Fortran (GCC) 10.3.1 20210420 May need narrowing down to affected versions.
