rui.zhang added a comment. > Well, if you can find a solution to the `void*` <-> `T**` problem, that might > make it tractable. Or you can introduce a flag to control whether we do this > — I guess on some level `-fstrict-aliasing` ought to be the full language > model, so this would mean introducing a `-fless-strict-aliasing` or something > like it.
Is it helpful if we only track pointers to user defined types so that `void *` or `char *` is not in the picture? Repository: rG LLVM Github Monorepo CHANGES SINCE LAST ACTION https://reviews.llvm.org/D122573/new/ https://reviews.llvm.org/D122573 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
