https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93388
--- Comment #18 from David Binderman <dcb314 at hotmail dot com> --- (In reply to Arseny Solokha from comment #17) > After the recent analyzer overhaul it's probably time to update this list > once again. Done. $ cat 20200814.ana.O2.c.out | fgrep "internal c" | fgrep analyzer ./c-c++-common/vector-subscript-3.c:5:16: internal compiler error: in validate, at analyzer/region-model.cc:243 ./gcc.c-torture/compile/20010107-1.c:7:3: internal compiler error: in get_or_create_mem_ref, at analyzer/region-model.cc:6932 ./gcc.dg/pr70022.c:9:3: internal compiler error: in validate, at analyzer/region-model.cc:243 ./gcc.dg/pr78526.c:10:1: internal compiler error: in validate, at analyzer/region-model.cc:243 ./gcc.target/i386/addr-space-5.c:13:3: internal compiler error: in get_or_create_mem_ref, at analyzer/region-model.cc:6932 ./gcc.target/i386/pr79498.c:9:1: internal compiler error: in validate, at analyzer/region-model.cc:243 $ So downto two crashes. I used flags -g -O2 -fanalyzer > Maybe trying each optimization level in turn besides -O2 might > also make sense. Maybe. One thing at a time. Let's get popular flags like -g -O2 working first. Then maybe -g -O3 then -g -O3 -march=native. Then when that's all working we can try out -fanalyzer on the source code of gcc. Just some ideas.
