https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86643
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Tobias Burnus from comment #1)
> Culprit is r262474 - "P0935R0 Eradicating unnecessarily explicit default
> constructors"
>
>
> Looking closer at the example, it doesn't use std::basic_ostringstream as
> advertised but:
> std::ostringstream buf2("test", std::ios_base::ate);
>
> The "std::ostringstream" is deprecated
What? No it isn't.
> and replacing it by
> std::basic_ostringstream<char> buf2("test", std::ios_base::ate);
> works.
>
>
> The question is whether the patch intended to remove the deprecated support
> for std::ostringstream or not. If it did, I think that warrens an entry at
> https://gcc.gnu.org/gcc-9/changes.html ; if not, then it needs to be fixed.
No support for anything has been removed. You need a clean build.
*** This bug has been marked as a duplicate of bug 86513 ***
