[Bug fortran/60913] [OOP] Memory leak with allocatable polymorphic function result (in type-bound operator)

2017-01-25 Thread cmacmackin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60913 --- Comment #9 from Chris --- Last I heard, gfortran still doesn't invoke finalisation in this situation. In any case, while (in my main code) I could certainly reduce the volume of leaked memory via finalisation (by deallocating arrays contained

[Bug fortran/60913] [OOP] Memory leak with allocatable polymorphic function result (in type-bound operator)

2017-01-25 Thread cmacmackin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60913 --- Comment #7 from Chris --- Damian, can you tell me where in the standard allocatable polymorphic results are prohibited with pure functions? I've been using them that way in my code, which compiles without issue using gfortran. I haven't teste

[Bug fortran/60913] [OOP] Memory leak with allocatable polymorphic function result (in type-bound operator)

2017-01-24 Thread cmacmackin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60913 --- Comment #5 from Chris --- Has there been any progress on this bug? It is making a large piece of scientific software I have written unusable for decent resolution simulations. I'm running gfortran 6.1.0, compiled with OpenCoarrays support. A

[Bug fortran/60913] [OOP] Memory leak with allocatable polymorphic function result (in type-bound operator)

2017-01-24 Thread cmacmackin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60913 Chris changed: What|Removed |Added CC||cmacmackin at gmail dot com --- Comment #4 from

[Bug fortran/78990] New: ICE when assigning polymorphic array function result

2017-01-04 Thread cmacmackin at gmail dot com
Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: cmacmackin at gmail dot com Target Milestone: --- Created attachment 40459 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40459&action=edit Minimal reproducer When a function returns a polymorphi

[Bug fortran/78395] [OOP] ICE for operations with polymorphic variables

2016-11-17 Thread cmacmackin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78395 --- Comment #6 from Chris --- > Which one do you mean exactly? Shouldn't they all use the user-defined > assignment function? Yes, that's right--they all should. Sorry, I didn't have the code up in front of me when I wrote that so I was a bit i

[Bug fortran/78395] [OOP] ICE for operations with polymorphic variables

2016-11-17 Thread cmacmackin at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78395 --- Comment #4 from Chris --- I tried compiling (my original example) on a different box, this one with gfortran 6.2.0 obtained from the ubuntu-toolchain-r/test PPA. I got Driving: gfortran-6 -v minimal.f90 -l gfortran -l m -shared-libgcc Using

[Bug fortran/78395] New: [OOP] ICE for operations with polymorphic variables

2016-11-17 Thread cmacmackin at gmail dot com
Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: cmacmackin at gmail dot com Target Milestone: --- Created attachment 40066 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40066&action=edit Minimal code producing ICE. While trying to produce a

[Bug fortran/66409] New: Reporting ambiguous interface when overloading assignment with polymorphic array

2015-06-03 Thread cmacmackin at gmail dot com
Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: cmacmackin at gmail dot com Target Milestone: --- I have come across what I believe to be a bug (or possibly a misunderstanding of the standard on one of our counts