https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85998
Jonathan Wakely changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85998
Jakub Jelinek changed:
What|Removed |Added
Target Milestone|9.0 |9.2
--- Comment #7 from Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85998
Jonathan Wakely changed:
What|Removed |Added
Status|RESOLVED|NEW
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85998
--- Comment #5 from Jeff Hammond ---
> Finishing C++17 support in libstdc++ is already one of our top priorities for
> GCC 9. There's no need to ask for it, and doing so won't affect priorities.
> The missing pieces are documented:
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85998
Jonathan Wakely changed:
What|Removed |Added
Target Milestone|--- |9.0
--- Comment #4 from Jonathan
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85998
--- Comment #3 from Jeff Hammond ---
Other projects use the existence of feature requests in their bug tracker for
prioritization of development. How does GCC manage this information? How do
you track GCC roadmap development if not through
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85998
Jonathan Wakely changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85998
--- Comment #1 from Andrew Pinski ---
https://gcc.gnu.org/ml/libstdc++/2017-11/msg00112.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85998
Andrew Pinski changed:
What|Removed |Added
Component|c++ |libstdc++
Severity|normal