------- Comment #10 from ian at airs dot com 2006-07-23 17:35 ------- I believe that patch is responsible because this behaviour does not happen in gcc 4.0.1, and it does happen in gcc 4.0.2, and that was the obvious change. I admit that I haven't actually tried reverting that specific patch to see what happens.
-- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26965
