FWIW, I agree with Richard here. We already have different defaults for which sanitizers are recoverable, and which are not (-fsanitize=addres, unreachable etc.). We may also have the defaults for which sanitizers trap-on-error (-fsanitize=cfi), and which print diagnostics. I think that adding `-fsanitize-trap=<list>` is the way to go. I would love to see the ugly mask `-fsanitize=undefined-trap` gone in one way or another. Instead, I'd vote for silently disabling `vptr` sanitizer if the user runs the invocation:
`clang++ -fsanitize=undefined -fsanitize-trap=undefined`. "Well, you're asking us to skip runtime checks and trap on error instead, we'll do that, but implicitly disable sanitizers which can't be implemented w/o runtime checks". http://reviews.llvm.org/D10268 EMAIL PREFERENCES http://reviews.llvm.org/settings/panel/emailpreferences/ _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
