https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64397
Paul Thomas changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64397
--- Comment #11 from Dominique d'Humieres ---
This PR seems to have been fixed by revision r268474.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64397
Dominique d'Humieres changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #10 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64397
Paul Thomas changed:
What|Removed |Added
Status|WAITING |NEW
Assignee|unassigned at gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64397
Dominique d'Humieres changed:
What|Removed |Added
Status|NEW |WAITING
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64397
janus at gcc dot gnu.org changed:
What|Removed |Added
Summary|[OOP] Runtime segfault with |[OOP] Runtime segfault with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64397
--- Comment #5 from patnel97269-gfortran at yahoo dot fr ---
(In reply to janus from comment #3)
Actually one can reduce it even further:
program main
type :: my_integer
real, allocatable :: x(:)
end type
type(my_integer) ::
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64397
--- Comment #6 from janus at gcc dot gnu.org ---
(In reply to patnel97269-gfortran from comment #5)
I agree that this example still trigger a bug, but I remember in my original
(more complicated) code, the segfault appears when it tries to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64397
--- Comment #7 from patnel97269-gfortran at yahoo dot fr ---
(In reply to janus from comment #6)
(In reply to patnel97269-gfortran from comment #5)
I agree that this example still trigger a bug, but I remember in my original
(more
