From: Marek Polacek <polacek@redhat.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GCC static analysis branch now available on Compiler Explorer
Date: Tue, 10 Dec 2019 16:04:00 -0000 [thread overview]
Message-ID: <20191210160443.GC1118066@redhat.com> (raw)
In-Reply-To: <8fd6dd19a5d97900d31159555783dda11c6316d6.camel@redhat.com>
On Tue, Dec 10, 2019 at 10:46:59AM -0500, David Malcolm wrote:
> For the adventurous/curious, my static analyzer branch of GCC [1] is
> now available on Compiler Explorer (aka godbolt.org) so you can try it
> out without building it yourself. [Thanks to Matt Godbolt, Patrick
> Quist and others at the Compiler Explorer project]
Congrats!
> On https://godbolt.org/ within the C and C++ languages, select
> "x86-64 gcc (static analysis)"
> as the compiler (though strictly speaking only C is in-scope right
> now). It's configured to automatically inject -fanalyzer (just on this
> site; it isn't the default in the branch).
>
> Some precanned examples:
> * various malloc issues: https://godbolt.org/z/tnx65n
> * stdio issues: https://godbolt.org/z/4BP-Tj
> * fprintf in signal handler: https://godbolt.org/z/ew7mW6
> * tainted data affecting control flow: https://godbolt.org/z/3v8vSj
> * password-leakage: https://godbolt.org/z/pRPYiv
> (the non-malloc examples are much more in "proof-of-concept" territory)
>
> Would it make sense to add an "analyzer" component to our bugzilla,
> even though this is still on a branch? (with me as default assignee)
I think so, we have it for e.g. JIT already, and it's probably just a matter
of time before the analyzer is merged.
--
Marek Polacek • Red Hat, Inc. • 300 A St, Boston, MA
next prev parent reply other threads:[~2019-12-10 16:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 15:47 David Malcolm
2019-12-10 16:04 ` Marek Polacek [this message]
2019-12-10 17:11 ` David Malcolm
2019-12-10 17:20 ` David Malcolm
2019-12-10 16:36 ` Martin Sebor
2019-12-10 17:57 ` David Malcolm
2019-12-10 19:51 ` Martin Sebor
2019-12-10 20:42 ` Jeff Law
2019-12-11 20:39 ` David Malcolm
2019-12-12 16:27 ` Martin Sebor
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=20191210160443.GC1118066@redhat.com \
--to=polacek@redhat.com \
--cc=dmalcolm@redhat.com \
--cc=gcc@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).