[Bug analyzer/105112] Speed up -fanalyzer on big-code.c

2022-03-31 Thread dmalcolm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105112 --- Comment #3 from David Malcolm --- Possible simplification: don't try to model floating-point operations e.g. any binop on a floating point value has unknown_svalue as the result, so that complicated floating-point computations can be

[Bug analyzer/105112] Speed up -fanalyzer on big-code.c

2022-03-30 Thread dmalcolm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105112 --- Comment #2 from David Malcolm --- FWIW, "perf report" shows that these are the top items in the profile: 8.72% libc-2.31.so [.] _int_malloc 6.68% libc-2.31.so [.] _int_free 2.91% cc1 [.] ana::binding_map::binding_map 2.76%

[Bug analyzer/105112] Speed up -fanalyzer on big-code.c

2022-03-30 Thread dmalcolm at gcc dot gnu.org via Gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105112 --- Comment #1 from David Malcolm --- Example state (picked at random from -fdump-analyzer-exploded-nodes-2 output): EN 113734: preds: EN: 113733 succs: EN: 113735 callstring: [] before (SN: 12511 stmt: 0): if (j_8254 <= 8191) 31 | for (j =