Re: [PATCH, Fortran, pr78395, v1] [OOP] error on polymorphic assignment

Whoops, hit send to fast. Here's the patch committed. - Andre On Sun, 20 Nov 2016 15:23:16 +0100 Andre Vehreschild wrote: > Hi Janus, > > thanks for the review. Committed to trunk as r242637. Will wait one week > before committing to 6. > > Regards, > Andre > > On Sat,

Re: [PATCH, Fortran, pr78395, v1] [OOP] error on polymorphic assignment

Hi Janus, thanks for the review. Committed to trunk as r242637. Will wait one week before committing to 6. Regards, Andre On Sat, 19 Nov 2016 16:14:54 +0100 Janus Weil wrote: > Hi Andre, > > > When checking the shortened example in comment #3 one gets a segfault, >

Re: [PATCH, Fortran, pr78395, v1] [OOP] error on polymorphic assignment

Hi Andre, > When checking the shortened example in comment #3 one gets a segfault, because > v6 is not allocated explicitly. The initial example made sure, that v6 was > allocated. sorry, I guess that's my fault. I blindly removed the allocate statement when looking for a reduced test case for

Re: [PATCH, Fortran, pr78395, v1] [OOP] error on polymorphic assignment

Hi Andre, Btw, when using the in gcc-7 available polymorphic assign, then v6 is actually auto-allocated and the program runs fine. So what are your opinions on the auto-allocation issue? It is my experience that such questions can speedily and correctly be answered by the regulars on

[PATCH, Fortran, pr78395, v1] [OOP] error on polymorphic assignment

Hi all, attached patch fixes the issue which was given by nesting calls to typebound procedures. The expression of the inner typebound procedure call was resolved correctly, but in the case of it's having a class type the ref-list was discarded. Leaving the list of references untouched, resolves