> Can you please identify the patch which fixed it on the mainline so we > can evaluate how risky it is? If it's not a candidate for 3.1.0, it may > be appropriate for 3.1.1. > This patch fixed it: http://gcc.gnu.org/ml/gcc-patches/2002-03/msg01087.html -eric -- Written using state-of-the-rat technology.