This bug has been fixed in upstream SVN for gcc 4.6, 4.7, and trunk (4.8).
Could the upstream fix be pulled in? (Will it automatically be pulled in the next time upstream posts a new minor-version release for these versions?)
This bug has been fixed in upstream SVN for gcc 4.6, 4.7, and trunk (4.8).
Could the upstream fix be pulled in? (Will it automatically be pulled in the next time upstream posts a new minor-version release for these versions?)