On Sun, Mar 9, 2014 at 11:49 AM, Logan Chien <[email protected]> wrote: > > Yes, but that test case was reduced from the other project with more > restricted license. Besides, that test case is not very reliable. It may > dependent on the heap usage of clang to trigger the issue. I am afraid that > it will be no longer meaningful when the clang code base grows.
The code itself looks fine, but I would prefer if we had a test case to ensure we didn't regress the behavior in the future. I would imagine there's a way to reproduce the issue that doesn't rely on heap usage? ~Aaron _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
