On 17/01/15 18:43, Anthony G. Basile wrote:
Hi everyone,
It looks like there aren't too many bugs against gcc-4.9 (bug #495124).
There are a couple having to do with lto and one which is hardened
specific, but its probably a good idea to start keywording on the
various arches so we can get more bug reports and not trail behind. So
I opened bug #536874.
I've followed Ryan's workflow where he has one bug for gcc 4.9 porting
and another for keywording/stabilization. I'm not sure why he did it
this way, but it may be less confusing in the future to have just one
which track the state of the ebuild from keyword masked, to keyworded to
stabilization.
@rhill, any advice here :)
Word of warning, asan was still terminally broken on nontrivial code
last time I tested it.
lu