http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58380
--- Comment #7 from Jeffrey A. Law <law at redhat dot com> --- 202296 doesn't change anything WRT sequencing of operations; it merely allows the threader to dive a bit deeper into the CFG to determine a final target for a jump threading opportunity. Presumably David bootstrapped the trunk, then built k3d? If so, then it might be a mis-compilation of GCC itself. As I mentioned in c#3 I'm looking at one of those right now. If this failure occurs in a stage1 cc1plus, then, well, that's totally different (and much easier to track down). Either way, it's mine.
