https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40897
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |egallager at gcc dot gnu.org
Resolution|--- |WORKSFORME
--- Comment #8 from Eric Gallager <egallager at gcc dot gnu.org> ---
Redoing lost comments:
https://gcc.gnu.org/ml/gcc-bugs/2017-08/msg01623.html
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2017-08-14
CC| |egallager at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #8 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #5)
> If it is getting you an internal error, then it is usually it is because the
> attachments are too big.
>
> As for the other issue, there is a C++ defect report about this case, which
> consider this as dependent but a member as non dependent and all confusing
> happens with namelookup and such.
Link to the C++ DR? Is it still open?
https://gcc.gnu.org/ml/gcc-bugs/2017-08/msg01625.html
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #9 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Roger Leigh from comment #6)
> Created attachment 18264 [details]
> Preprocessed source for g++-4.5.0 (svn 149777)
This compiles successfully without error for me with g++-8 (svn 250985), so I
guess I can close it.
