A reduced test case wouldn't be that useful since stack overflows are dependent on the system under test. Since you have access to the code, you can rerun Clang with all the warnings on (with "-Weverything") and just disable this warning (with "-Wno-infinite-recursion"). This will show if all the other warnings can handle your large CFG.
On Wed, Jul 22, 2015 at 3:07 PM, Vedant Kumar <v...@apple.com> wrote: > On Jul 22, 2015, at 2:50 PM, Richard Trieu <rtr...@google.com> wrote: > > > > Is the code that produces the large CFG available? It may be useful to > test that other users of the CFG can cope with processing the code. > > Sadly no :(. > > Clang gave up after checking a little less than 25,000 CFGBlocks. > > Would you like me to try and reproduce this behavior with a simplified > test case?
_______________________________________________ cfe-commits mailing list cfe-commits@cs.uiuc.edu http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits