According to this (https://gcc.gnu.org/ml/gcc/2017-04/msg00080.html) release announcement, and the main GCC page itself, GCC 7.0.1, the first release in the GCC7 line, was officially issued on 4/20. Acutely understanding how disruptive the GCC 5 and GCC 6 releases were, I can well understand how vetting major version bumps in GCC might take more time, these days. Ordinarily, I wouldn't even consider filing this bug, except that I don't even see an experimental ebuild in the toolchain overlay. All in all, GCC 7's changes (https://gcc.gnu.org/gcc-7/changes.html) don't seem to be anywhere near as disruptive as those introduced in the previous major-version bumps, but that may just be optimism on my part. That said, GCC7 is looking to be the flagship for C++17 implementation and I do a lot of work with experimental C++ features, so this release is kind of important for me. I more than understand I'm taking my system into my own hands adopting a new compiler version so early on in a source distro, but I've already suffered that with GCC 5 and only barely finished with GCC 6, so I really don't mind.
From https://gcc.gnu.org/gcc-7/: "As of this time no releases of GCC 7 have yet been made." Impossible to bump what's not released yet. There are only RCs now. See also https://bugs.gentoo.org/show_bug.cgi?id=601308
(In reply to Coacher from comment #1) > From https://gcc.gnu.org/gcc-7/: > "As of this time no releases of GCC 7 have yet been made." > Impossible to bump what's not released yet. There are only RCs now. > > See also https://bugs.gentoo.org/show_bug.cgi?id=601308 I may have initially jumped the gun by a small amount, but if you refresh that page I, at least, am seeing the following: > May 2, 2017 > > The GNU project and the GCC developers are pleased to announce the release of GCC > 7.1. > > This release is a major release, containing new features (as well as many other improvements) relative to GCC 6.x.
