------- Comment #2 from pcarlini at suse dot de 2006-09-12 15:10 ------- To be 100% sure, we checked again gcc4.1.1 both on x86-linux and powerc-darwin and the bug is definitely not there (anymore)
-- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29035
