public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mir Immad <mirimnan017@gmail.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: GSoC: Working on the static analyzer
Date: Fri, 14 Jan 2022 22:15:31 +0530	[thread overview]
Message-ID: <CAE1-7oxt_tHSnDsP6WXwADfK8GAA+4Yd0aXdL3tGrqxW_UO-uw@mail.gmail.com> (raw)
In-Reply-To: <4eec5fa69b9daedcec5361c2cc18df7f1ef397af.camel@redhat.com>

HI David,
I've been tinkering with the static analyzer for the last few days. I find
the project of adding SARIF output to the analyzer intresting. I'm writing
this to let you know that I'm trying to learn the codebase.
Thank you.

On Tue, Jan 11, 2022, 7:09 PM David Malcolm <dmalcolm@redhat.com> wrote:

> On Tue, 2022-01-11 at 11:03 +0530, Mir Immad via Gcc wrote:
> > Hi everyone,
>
> Hi, and welcome.
>
> > I intend to work on the static analyzer. Are these documents enough to
> > get
> > started: https://gcc.gnu.org/onlinedocs/gccint and
> >
> https://gcc.gnu.org/onlinedocs/gccint/Analyzer-Internals.html#Analyzer-Internals
>
> Yes.
>
> There are also some high-level notes here:
>   https://gcc.gnu.org/wiki/DavidMalcolm/StaticAnalyzer
>
> Also, given that the analyzer is part of GCC, the more general
> introductions to hacking on GCC will be useful.
>
> I recommend creating a trivial C source file with a bug in it (e.g. a
> 3-line function with a use-after-free), and stepping through the
> analyzer to get a sense of how it works.
>
> Hope this is helpful; don't hesitate to ask questions.
> Dave
>
>

  reply	other threads:[~2022-01-14 16:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-11  5:33 Mir Immad
2022-01-11 13:39 ` David Malcolm
2022-01-14 16:45   ` Mir Immad [this message]
2022-01-17  0:11     ` David Malcolm
     [not found]       ` <CAE1-7ozOGbp-sypHeWxJpoLWzNbqYtWrrsnhLK9RdhYrLe6z1w@mail.gmail.com>
2022-01-23 20:11         ` Mir Immad
2022-01-24 14:19           ` Ankur Saini
2022-01-26 14:31             ` David Malcolm
2022-01-26 14:26           ` David Malcolm
2022-01-29 14:52             ` Mir Immad
2022-01-29 17:39               ` David Malcolm
2022-02-01 14:58                 ` Mir Immad
2022-02-13 15:46                   ` Mir Immad
2022-02-13 22:57                     ` David Malcolm
2022-02-13 23:05                       ` David Malcolm
2022-04-04 16:16                         ` Mir Immad
2022-04-08 18:19                           ` David Malcolm
     [not found] <mailman.6588.1644793069.2100866.gcc@gcc.gnu.org>
2022-02-14 12:59 ` Basile Starynkevitch
2022-02-14 13:12   ` Basile Starynkevitch

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=CAE1-7oxt_tHSnDsP6WXwADfK8GAA+4Yd0aXdL3tGrqxW_UO-uw@mail.gmail.com \
    --to=mirimnan017@gmail.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).