-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/09/11 15:10, Paolo Bonzini wrote: > On 11/09/2011 06:53 PM, Jeff Law wrote: >> My patch totally ignores the other code on the unexecutable path. >> So we can miss externally visible side effects, if we were to >> somehow get on the unexecutable path. But that's the whole >> point, in a conforming program we can't ever get on the >> unexecutable path. > > But if a subroutine call never returns, we wouldn't get to the > undefined behavior in the first place. Yea, I'd been pondering this aspect as well. The cases that most concern me would be aborts and infinite loops.
Stuff like EH is represented in the CFG and the control dependence stuff would ensure we do the right thing. I think there are enough unanswered questions that we should defer this until after 4.7 branches. Or at the least not have the option on by default for 4.7, even if the issues raised in the threads are addressed. Jeff -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOvBvtAAoJEBRtltQi2kC7kmUH/j4KOxLwlgLJZmYEp1fPAvOp riga57XaawnZtxnZYDwD8TQ8l5a2lsj8LMUthBUFq6Bl8NLTh4uJRAtWLbhS9D7Q t1sl+2D2CjzdX4J2Ygs7asKrPld+OIFizttu6pYw9CZ2o4Ia21xnmLnDqtbkBiC6 BZ+qGtzjMetEZQhsQYYz8q/B44eF5Cnfsl5ISaKVaF2ZfR3dZGhoxqujuD1/bZtQ Rijrg6uddiLQZrMvKT9WiJL+eoZYUvB1tTLD8tRs7e2YPSmQuxpmcN4JKc+DsPEF d+n1ZWYSG2EmoHCaHwkSq0X5oxGjNz+hfbSpyM+sVXEubilM1BiEBvwegK22GWo= =lPeq -----END PGP SIGNATURE-----
