rsmith added a comment.
I don't like calling this a "TBAA sanitizer". What we're sanitizing is the
object model and effective type rules; it seems irrelevant which specific
compiler analysis passes would result in your program misbehaving if you break
the rules. I would also expect that we will extend this in future to assign
types to storage even in cases where there is no store (for instance, we should
be able to catch `float f() { int n; return *(float*)&n; }` despite there being
no TBAA violation in the naive IR).
How about renaming this to something more like `-fsanitize=type`?
https://reviews.llvm.org/D32199
_______________________________________________
cfe-commits mailing list
cfe-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
