https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85998
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jeff Hammond from comment #3)
> Other projects use the existence of feature requests in their bug tracker
> for prioritization of development. How does GCC manage this information?
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/onlinedocs/libstdc++/manual/status.html#status.iso.2017
> How do you track GCC roadmap development if not through this system?
However different developers want to. People work on what they (or their
employers or sponsors) want to work on. Personally I don't see any point in
having open bugs to track that features are missing when they're already
documented as missing. We know they're missing.
If it makes you feel better this can be reopened, and then ignored until the
missing features are done, then closed as FIXED. I don't see any advantage to
that though.
> Where
> can I follow progress towards C++17 parallel STL?
On the libstdc++ mailing list, and (especially during the initial stages of the
integration) in the PSTL upstream.
> I am well aware of the Intel PSTL work.
So then you might have seen the pull requests being created to prepare it for
inclusion in libstdc++ and libc++.
