> Indeed, I agree. By the way (for people not following on a daily basis > the audit trail of this bug), yesterday I have been able to reproduce > the problem, exactly as originally presented, on an x86-machine using > stock glibc2.3.5... and the patch fixes it, of course. Me too. Please check this in to both mainline and gcc-4_0-branch. -benjamin