Actually, forget that - this bug isn't specific to gcc 4.8 anyway if it's occurring on precise. So, most definitely another issue. Sigh
Actually, forget that - this bug isn't specific to gcc 4.8 anyway if it's occurring on precise. So, most definitely another issue. Sigh