Just a short update: I ran this over our internal codebase, and found a roughly 0.5% change in warnings. All the ones I investigated were new warnings of the form: SomeType x = ...; CHECK(some.Other() || something.Else()); // this is the macro that evaluates to a no-return destructor iff the condition is false ... doSomethingWith(x);
And now we would get a warning that 'x' is never used after being initialized (I assume because it now always thinks the noreturn dtor is run). I'll have to investigate some more. Cheers, /Manuel http://reviews.llvm.org/D3627 _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
