[Bug fortran/108649] allocation segmentation fault for pointer derive type and ICE for final-binding

2023-02-03 Thread Boyce at engineer dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108649 --- Comment #8 from Scott Boyce --- Sorry for sending a second message, my test cases have a workaround already added to the code for the Finalization, but the code posted has issues with ALLOCATION of derived types.

[Bug fortran/108649] allocation segmentation fault for pointer derive type and ICE for final-binding

2023-02-03 Thread Boyce at engineer dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108649 --- Comment #7 from Scott Boyce --- (In reply to Jerry DeLisle from comment #6) Thanks that is excellent news about the finalization. There also is the issue with the ALLOCATION as well. Another set of test cases are my Batteries Included

[Bug fortran/108651] Array Constructor with [type-spec:: fails to apply to all values, eg x = [integer(int64):: 1,2,3,4]

2023-02-03 Thread Boyce at engineer dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108651 --- Comment #3 from Scott Boyce --- No its not correct because the [integer(int64):: in INTEGER(INT64), dimension(2), parameter:: arr1 = [integer(int64):: -3300711175878204139, 8258803693257250632] is the initialization is indicating that

[Bug fortran/108649] allocation segmentation fault for pointer derive type and ICE for final-binding

2023-02-02 Thread Boyce at engineer dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108649 --- Comment #5 from Scott Boyce --- Comment on attachment 54395 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54395 Source Part 1 This is a part 1 of a 3 part zip file created with 7zip

[Bug fortran/108652] New: type-bound procedure that returns integer used to allocate character on stack

2023-02-02 Thread Boyce at engineer dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108652 Bug ID: 108652 Summary: type-bound procedure that returns integer used to allocate character on stack Product: gcc Version: 11.3.0 Status: UNCONFIRMED

[Bug fortran/108651] New: Array Constructor with [type-spec:: fails to apply to all values, eg x = [integer(int64):: 1,2,3,4]

2023-02-02 Thread Boyce at engineer dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108651 Bug ID: 108651 Summary: Array Constructor with [type-spec:: fails to apply to all values, eg x = [integer(int64):: 1,2,3,4] Product: gcc Version: 11.3.0 Status:

[Bug fortran/108650] New: Error: IMPORT statement only permitted in an INTERFACE body | but it should be allowed in any contained routine to control scope

2023-02-02 Thread Boyce at engineer dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108650 Bug ID: 108650 Summary: Error: IMPORT statement only permitted in an INTERFACE body | but it should be allowed in any contained routine to control scope Product: gcc

[Bug fortran/108649] allocation segmentation fault for pointer derive type and ICE for final-binding

2023-02-02 Thread Boyce at engineer dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108649 --- Comment #4 from Scott Boyce --- Created attachment 54397 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54397=edit Source Part 3

[Bug fortran/108649] allocation segmentation fault for pointer derive type and ICE for final-binding

2023-02-02 Thread Boyce at engineer dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108649 --- Comment #3 from Scott Boyce --- Created attachment 54396 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54396=edit Source Part 2

[Bug fortran/108649] allocation segmentation fault for pointer derive type and ICE for final-binding

2023-02-02 Thread Boyce at engineer dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108649 --- Comment #2 from Scott Boyce --- Created attachment 54395 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54395=edit Source Part 1

[Bug fortran/108649] allocation segmentation fault for pointer derive type and ICE for final-binding

2023-02-02 Thread Boyce at engineer dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108649 --- Comment #1 from Scott Boyce --- Missing attachment in first post I was unable to compress the source code to 1MB. So I will make it into a mutlipart zip over the next three posts. If you want to download a single zip file, it is located

[Bug fortran/108649] New: allocation segmentation fault for pointer derive type and ICE for final-binding

2023-02-02 Thread Boyce at engineer dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108649 Bug ID: 108649 Summary: allocation segmentation fault for pointer derive type and ICE for final-binding Product: gcc Version: 11.3.0 Status: UNCONFIRMED

[Bug fortran/96255] [F2018] Implement optional type spec for index in DO CONCURRENT

2023-02-02 Thread Boyce at engineer dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96255 Scott Boyce changed: What|Removed |Added CC||Boyce at engineer dot com --- Comment #10

[Bug fortran/99609] Pure Function that has a Variable with Value Attribute that is modified

2021-03-17 Thread Boyce at engineer dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99609 --- Comment #3 from Scott Boyce --- Yeah that is the same bug request. Though it is for version 11, any chance of back-porting to version 9 and 10?

[Bug fortran/99609] New: Pure Function that has a Variable with Value Attribute that is modified

2021-03-15 Thread Boyce at engineer dot com via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99609 Bug ID: 99609 Summary: Pure Function that has a Variable with Value Attribute that is modified Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal