Created attachment 380380 [details] emerge --info nss throws a bunch of -Wstrict-aliasing warnings with gcc-4.8.3 Here is an interesting discussion on analogous issue in nspr (and nss): https://bugzilla.mozilla.org/show_bug.cgi?id=439144 * QA Notice: Package triggers severe warnings which indicate that it * may exhibit random runtime failures. * mpi/mpcpucache.c:681:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] * mpi/mpcpucache.c:682:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] * mpi/mpcpucache.c:683:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] * sslsnce.c:1232:5: warning: dereferencing type-punned pointer will break strict-aliasing rules [-Wstrict-aliasing] etc. Proposed solution: inherit flag-o-matic append-flags -fno-strict-aliasing or append them only for affected files.
The same output would also tell you not to file a bug report here, but upstream.
Which doesn't mean nss should remain broken when it can be easily fixed. These warnings take years to iron out (see link) and there are real bugs behind them. (Bug 270098) grep -r "fno-strict-aliasing" * | wc -l in the main portage tree yields 636 so I assume it's common practice.
