------- Comment #22 from peeterj at ca dot ibm dot com 2008-01-16 00:04 ------- re: Fixed on the mainline. I'm not sure we want to put this on the other branches.
Not knowing the gcc code in question, I can't comment on how much potential regression risk this fix will introduce. Assuming it's safe enough to apply without worry to other releases, I'd hope this would also be applied also to gcc-4.2 . The 4.2 version is what we were attempting to use when the bug was encountered, and switching to 4.3 at this point would likely be more destabilizing than the original bug (as well as potentially being a porting exersize as has traditionally been the case between major compiler revisions). -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31309
