------- Comment #6 from amylaar at gcc dot gnu dot org 2006-07-25 12:14 ------- (In reply to comment #5) > I am not going to track down what did it, but something has fixed this on the > 4.2 branch. I can reproduce it on Debian's 4.1 branch snapshot. If someone > wants to fix it on 4.1, it should probably be easy to use the regression > hunter > to identify what patch caused the string "problem" to appear in the assembly > output. It is probably something in the last two and a half months, since the > bug was reported, but I do not see any obvious candidates. > If this is fixed on mainline, the fix must be rather recent; I see this still failing with r115417: GNU C++ version 4.2.0 20060713 (experimental). What is the oldest gcc 4.2 version where you saw this work?
-- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27574
