public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "asolokha at gmx 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: Mon, 28 Sep 2020 11:03:15 +0000	[thread overview]
Message-ID: <bug-93388-4-tovBrzjJFE@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 #22 from Arseny Solokha <asolokha at gmx dot com> ---
(In reply to David Binderman from comment #21)
> So given that the analyzer doesn't crash on the current Linux kernel code,
> does it do anything useful like find any bugs, perhaps ?

The snapshot I've mentioned is the first one ever which has gotten to be able
to build whole allyesconfig Linux w/ -fanalyzer w/o any ICE. I didn't try to
check its reports on Linux up until now. Analyzer still has some issues like
the one I reported in PR93695 which constitutes a heavy dose of false positives
in my testing.

  parent reply	other threads:[~2020-09-28 11:03 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
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 [this message]
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-tovBrzjJFE@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: link
Be 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).