https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82064
--- Comment #6 from paul.richard.thomas at gmail dot com <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 On 5 September 2017 at 14:25, janus at gcc dot gnu.org <gcc-bugzi...@gcc.gnu.org> wrote: > 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, in particular the changes to >> > resolve_select_type, makes the error go away. >> >> Strangely, my GNU Fortran (GCC) 8.0.0 20170830 gives me two "OK"s :-) > > Also on the version with separate files? > > >> That said, this is a repeat of another recent bug (sorry, I am rushing off >> to work - no time to find the number). I posted a work around, which >> translates in this case to: >> >> [..] >> >> The permanent fix is to make sure that the vtables get produced >> unconditionally for module derived types. > > I thought we already did that, but probably we're still missing some cases? > > -- > You are receiving this mail because: > You are on the CC list for the bug.
