[Bug fortran/102510] Function call has unnecessary stride check

2021-09-29 Thread anlauf at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102510 anlauf at gcc dot gnu.org changed: What|Removed |Added Status|NEW |RESOLVED

[Bug fortran/102510] Function call has unnecessary stride check

2021-09-28 Thread dwwork at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102510 --- Comment #4 from Dalon Work --- No, I don't think there is more to expect. My mistaken assumption was that the return value of the function had to be a contiguous array of 8 elements. I don't find this to be a stupid assumption, since the

[Bug fortran/102510] Function call has unnecessary stride check

2021-09-28 Thread anlauf at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102510 --- Comment #3 from anlauf at gcc dot gnu.org --- It helps to look at the (Fortran) context. As written, the subroutine version is declared with explicit size contiguous arrays. If the caller has a non-contiguous (strided) result array, it

[Bug fortran/102510] Function call has unnecessary stride check

2021-09-28 Thread dwwork at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102510 --- Comment #2 from Dalon Work --- Thanks for the information. Based on your comments, I've created 2 new subroutines that call the "bad" function. The first places the result in a contiguous array, while the second places the result in a

[Bug fortran/102510] Function call has unnecessary stride check

2021-09-28 Thread rguenth at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102510 Richard Biener changed: What|Removed |Added Last reconfirmed||2021-09-28 Ever confirmed|0