public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug analyzer/93388] ensure -fanalyzer works with our C code Date: Fri, 14 Aug 2020 09:00:21 +0000 [thread overview] Message-ID: <bug-93388-4-M2Wjr0l5M7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-93388-4@http.gcc.gnu.org/bugzilla/> 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.
next prev parent reply other threads:[~2020-08-14 9:00 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-93388-4@http.gcc.gnu.org/bugzilla/> 2020-05-08 8:22 ` dcb314 at hotmail dot com 2020-08-14 3:40 ` asolokha at gmx dot com 2020-08-14 9:00 ` dcb314 at hotmail dot com [this message] 2020-08-14 18:42 ` dcb314 at hotmail dot com 2020-09-28 10:20 ` asolokha at gmx dot com 2020-09-28 10:42 ` dcb314 at hotmail dot com 2020-09-28 11:03 ` asolokha at gmx dot com 2020-10-14 20:39 ` cvs-commit at gcc dot gnu.org 2020-10-14 20:57 ` dmalcolm at gcc dot gnu.org 2020-10-14 21:05 ` dmalcolm at gcc dot gnu.org 2020-10-14 21:34 ` dcb314 at hotmail dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-93388-4-M2Wjr0l5M7@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).