From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) by sourceware.org (Postfix) with ESMTPS id 9C1353858D35 for ; Fri, 14 Jan 2022 16:45:42 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 9C1353858D35 Received: by mail-ed1-x532.google.com with SMTP id 15so2809149edx.9 for ; Fri, 14 Jan 2022 08:45:42 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=MYW9GGidaJ8aeeQkI4aOG9WSiSLwf70EwDTCVgEfU6Q=; b=QmEHl2CG9R2tgiIFU7hJl0qN0qI8KMpsYdgpx2yK3uUf7CARc8VBTT0x2ZJSxAizHu ose7bHxH7YP8wkDPw7hTBA03khstd/adRsc6zukIy5Xu3n7t0Nd1Ws5po8bfW6h9pnT/ SLkRUY+TxOjvp8WSfdrzDdMfeYJxEnt0/BI6mFV+oAyRRi1APafBYIpgEgt2wvrPIX4u +DatC1rI/ZROYQ+1Ht1u6UJUCUoRohjEOIDigM0fqaZZGj+J13bqqYUxw1obSx0Zu6r0 OGaqhuJs+Sk6sUrwRCeXaaqtodIF7dnPsDqyg+1GAfpml/reJbe0/mjQVIDGUR3cvhIs QQpA== X-Gm-Message-State: AOAM53285VtBYsj9AoRuRAQt4+tpOdzp4jNLLnxWPFJJHPq4eMnC/mSs 7GUCb3GnCn6WhKpvKe0VMRpqiXkbnUMb7RDhji8= X-Google-Smtp-Source: ABdhPJyk1eOTKnbEeVoNTPQQ81ppB2yoEChiUSDJsmJCIfb68xG/C3oDN83ihWXH42yvccPWp2bIoL1wQo1vp4MjiyM= X-Received: by 2002:aa7:db8b:: with SMTP id u11mr9923517edt.180.1642178741716; Fri, 14 Jan 2022 08:45:41 -0800 (PST) MIME-Version: 1.0 References: <4eec5fa69b9daedcec5361c2cc18df7f1ef397af.camel@redhat.com> In-Reply-To: <4eec5fa69b9daedcec5361c2cc18df7f1ef397af.camel@redhat.com> From: Mir Immad Date: Fri, 14 Jan 2022 22:15:31 +0530 Message-ID: Subject: Re: GSoC: Working on the static analyzer To: David Malcolm Cc: gcc@gcc.gnu.org X-Spam-Status: No, score=-0.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM, HTML_MESSAGE, KAM_SHORT, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.29 X-BeenThere: gcc@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Jan 2022 16:45:44 -0000 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 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 > >