------- Comment #13 from pinskia at gcc dot gnu dot org 2006-11-30 18:31 ------- (In reply to comment #12) > The code has not undefined behavior, but I think removing the check is ok > (it's > certainly not supposed to trigger _inside_ the assignment operator or the > copy constructor).
Actually I don't think removing that check is ok. Allows us to find problems with the gimplifier, when it is trying to create a temprorary variable when it should not. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30017
