From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B9EB83857016; Fri, 14 Aug 2020 09:00:21 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B9EB83857016 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1597395621; bh=GfmvMwW+y7COLfxwzoh1Q6xEEErn4HGTa3aFflIoKWY=; h=From:To:Subject:Date:In-Reply-To:References:From; b=ckyu5zFJaKvxC9ZxjzNAtLALU8zZiRXoJT0C82eXh94C9/1ZKRDGBmV9F+QcqZWao Nl0gGCx2d/HMEfZAIPjqxk8mypzglMooOelWf3lJgw5eUdy0yD+0f4uqsSzBR7pzTI YLMS0zXWtsoDjlXPK7LkjvDH0KRneYckUwbqXNfE= From: "dcb314 at hotmail dot com" 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: analyzer X-Bugzilla-Version: 10.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: dcb314 at hotmail dot com X-Bugzilla-Status: ASSIGNED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: gcc-bugs@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-bugs mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Aug 2020 09:00:21 -0000 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D93388 --- Comment #18 from David Binderman --- (In reply to Arseny Solokha from comment #17) > After the recent analyzer overhaul it's probably time to update this list > once again.=20 Done.=20 $ cat 20200814.ana.O2.c.out | fgrep "internal c" | fgrep analyzer ./c-c++-common/vector-subscript-3.c:5:16: internal compiler error: in valid= ate, 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 fir= st. Then maybe -g -O3 then -g -O3 -march=3Dnative. Then when that's all working we can try out -fanalyzer on the source code of gcc. Just some ideas.=