[Bug fortran/82064] [7/8 Regression] [OOP] multiple incompatible definitions of extended derived type via module use

2018-01-25 Thread rguenth at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82064 Richard Biener changed: What|Removed |Added Target Milestone|7.3 |7.4 --- Comment #9 from Richard Biener

[Bug fortran/82064] [7/8 Regression] [OOP] multiple incompatible definitions of extended derived type via module use

2017-10-03 Thread janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82064 --- Comment #8 from janus at gcc dot gnu.org --- (In reply to janus from comment #7) > ... which indeed fixes the issue with 'test_sep'. (Note: I have not > regtested it yet, but I hope it will not break anything.) To the contrary, it

[Bug fortran/82064] [7/8 Regression] [OOP] multiple incompatible definitions of extended derived type via module use

2017-10-03 Thread janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82064 --- Comment #7 from janus at gcc dot gnu.org --- (In reply to Paul Thomas from comment #4) > The permanent fix is to make sure that the vtables get produced > unconditionally for module derived types. This is accomplished by the following patch

[Bug fortran/82064] [7/8 Regression] [OOP] multiple incompatible definitions of extended derived type via module use

2017-09-06 Thread paul.richard.thomas at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82064 --- Comment #6 from paul.richard.thomas at gmail dot com --- Aaaah! I missed the point wrt separate files. As far as I remember, we make sure that class or derived entities get their vtable but not unreferenced type declarations. Cheers Paul

[Bug fortran/82064] [7/8 Regression] [OOP] multiple incompatible definitions of extended derived type via module use

2017-09-05 Thread janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82064 --- Comment #5 from janus at gcc dot gnu.org --- (In reply to Paul Thomas from comment #4) > (In reply to janus from comment #3) > > It appears that the regression has been introduced by r241450, which was the > > fix for PR 69834. Reverting it,

[Bug fortran/82064] [7/8 Regression] [OOP] multiple incompatible definitions of extended derived type via module use

2017-09-05 Thread pault at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82064 --- Comment #4 from Paul Thomas --- (In reply to janus from comment #3) > It appears that the regression has been introduced by r241450, which was the > fix for PR 69834. Reverting it, in particular the changes to > resolve_select_type, makes

[Bug fortran/82064] [7/8 Regression] [OOP] multiple incompatible definitions of extended derived type via module use

2017-09-04 Thread jakub at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82064 Jakub Jelinek changed: What|Removed |Added Priority|P3 |P4 CC|

[Bug fortran/82064] [7/8 Regression] [OOP] multiple incompatible definitions of extended derived type via module use

2017-09-03 Thread janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82064 janus at gcc dot gnu.org changed: What|Removed |Added Keywords|rejects-valid |wrong-code

[Bug fortran/82064] [7/8 Regression] [OOP] multiple incompatible definitions of extended derived type via module use

2017-09-02 Thread janus at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82064 janus at gcc dot gnu.org changed: What|Removed |Added Status|UNCONFIRMED |NEW Last reconfirmed|