------- Comment #5 from davidxl at gcc dot gnu dot org 2009-03-24 21:25 ------- (In reply to comment #3) > It might be better to place the check after the loop (and put an assert in > set_copy_of_val that triggers the copy may not happen). >
This sounds good. David -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39548
