https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70328
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |INVALID
--- Comment #4 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Morwenn from comment #3)
> Looks like providing a testcase will be hard: I switched to GCC 7.1 since
> then, and can't reproduce the bug anymore, be it in C++14 or C++17 mode.
> That said, a few things have changed since then and they may be involved in
> the failure to reproduce the bug:
> * My testsuite has changed since then, but I don't think that the tests that
> triggered the problem have changed at all
> * I regularly update my test framework (Catch), which has changed
> significantly these last months
>
> Either one of these changes hides the bug, or it has been fixed. I wasn't
> able to produce a minimal example back then, so it might be either.
OK, so I'll close this as INVALID then since there's no example. Although
probably WORKSFORME could work too. Or actually a lot of the different
resoultion statuses make sense. I dunno. I'll just stick with my first
instinct.
