- User Since
- May 18 2022, 9:07 PM (43 w, 6 d)
Wed, Mar 8
Oct 21 2022
Sep 16 2022
Thanks for fixing it.
Aug 29 2022
Your change looks great to me. Thanks for improving this case.
Jul 5 2022
I like the direction where this change is leading to and hope there is some way to land it incrementally. Since BuiltinType has the above mentioned concern on void *, how about we focus on RecordType pointers as a first step instead? Are there any pitfalls if we distinguish RecordType pointers by depth?
Jun 29 2022
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?