samsonov added a comment. That is, I presume it's highly unlikely user will need to have fine-grained setup for deciding which UBSan checks should be merged, and which should not. So, probably having a single `-fsanitize-merge-traps` / `-fno-sanitize-merge-traps` option would be enough. I'd like to hear other opinions, though.
In http://reviews.llvm.org/D15208#305199, @eugenis wrote: > Better -fsanitize-merge-checks, and it should apply to non-trap checks as > well (i.e. SIGILL address should uniquely correspond to the failure source > location). Just to make sure I understand it, you suggest to eventually pass it down to ASan/MSan instrumentation passes? Repository: rL LLVM http://reviews.llvm.org/D15208 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
