[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 dec

[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 stride

[Bug fortran/102510] New: Function call has unnecessary aliasing check

2021-09-27 Thread dwwork at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102510 Bug ID: 102510 Summary: Function call has unnecessary aliasing check Product: gcc Version: 11.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: f

[Bug c++/97477] g++ doesn't accept __restrict keyword inside array function parameter

2020-10-19 Thread dwwork at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97477 --- Comment #2 from Dalon Work --- (In reply to Richard Biener from comment #1) > IIRC restrict is not official C++ but I agree it should be accepted. You are correct, it is not official c++. g++ accepts and uses the '__restrict' keyword in c++

[Bug c++/97477] New: g++ doesn't accept __restrict keyword inside array function parameter

2020-10-17 Thread dwwork at gmail dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97477 Bug ID: 97477 Summary: g++ doesn't accept __restrict keyword inside array function parameter Product: gcc Version: 10.2.0 Status: UNCONFIRMED Severity: normal