This is a known issue with gcc-5.4.0 (as well as gcc-6.1.0) and is fixed upstream for gcc-5.5. https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71442 Is it possible to get this patch added to the ebuild for gcc-5.4? This is a nice debugging warning when developing.
Upstream pushed a fix for this in June. Can this be backported to 5.4.0?
Fixed in gcc 5.4.0-r2
we're going to roll this back
added in 5.4.0-r3 patchset 1.3