- User Since
- Mar 4 2015, 5:47 AM (236 w, 6 d)
Wed, Sep 4
Hi Hans, I am not too familiar with all windows path naming variants. Did you really observe a '\\?UNC\xxxx' path ?
Jun 12 2019
Jun 4 2019
Sep 26 2018
Sep 17 2018
Sep 16 2018
Compare following testcases (which should have an equivalent result):
Aug 7 2018
could one of you commit this change ?
Jul 27 2018
You just need to remember to take a copy of the 'comments' in your file and to copy those manually. Otherwise, the test driver is gone (as I noticed the hard way).
Reduced function attributes.
Jul 26 2018
Reassembled to reset the debug id's
Jul 24 2018
Found one extra line of debug info that could be removed.
Reduced the debug information.
Jul 20 2018
- Updated existing (related) testcase to actually test something
- Added new testcase showing the problem
Jul 19 2018
Jul 18 2018
Jun 21 2018
How about using an empty 'CHECK-NEXT:' statement for this ?
Jun 5 2018
Aug 7 2017
Hi Hal, I found an issue with this part when analyzing two pointers that are 'derived from each other', but are used in different loops.
Following code would go wrong:
Oct 17 2016
Maybe 'passthrough' should return a boolean, indicating that we need to stop or not. (see code comment)
The places where it is called could become something like: 'if (passthrough()) return;
Mar 17 2015
Further investigation shows that llvm/lib/Analysis/TypeBasedAliasAnalysis.cpp is not ready to handle struct types where multiple members have the same (0) offset. The clang fix only makes sense once that issue is resolved.