http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52822
--- Comment #4 from Paolo Carlini <paolo.carlini at oracle dot com> 2012-04-01 22:09:45 UTC --- PS: then shall we just do the assignment only when __result1 != __first, or algorithmically we can do better? In case we can also imagine having the trivial fix for 4.6 and maybe even 4.7.1 and committing it to mainline too without considering the issue resolved, in case later on somebody figures out something smarter algorithmically.
