------- Comment #3 from caroline dot rioux at ca dot ibm dot com 2009-02-18 22:02 ------- (In reply to comment #2) > Fixed in 4.1.0 as mentioned already. 3.3.x is no longer maintained and any > bug > that is reported against that old version is most likely not going to be ever > fixed. >
Ok thanks for your input. Was this explicitly fixed or a result of other framework changes? Is there any way a patch exists and could be applied? I ask because it is unlikely we will move to gcc4 in the short term. Is gcc3.4.x still supported? Because it also occurs there. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39237
