From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pg1-x536.google.com (mail-pg1-x536.google.com [IPv6:2607:f8b0:4864:20::536]) by sourceware.org (Postfix) with ESMTPS id A40413858C2C for ; Fri, 15 Apr 2022 17:06:46 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org A40413858C2C Received: by mail-pg1-x536.google.com with SMTP id 32so7779589pgl.4 for ; Fri, 15 Apr 2022 10:06:46 -0700 (PDT) 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=lWQNC8p8qF5n3IWfiV/+oqvEPHt+4O+a6rstKuZUzi4=; b=rbN2K92tdxubs5QuruRV0efllk4O/p9K8gPEp2NvF3RbkE096g5t8lmDBck9aU5k7v jX4dm6Gx7Az/GOAy930Rw9L+9UJRA3kPnQw2Z+sRhrw6y/vQf7rU05fhFYM/vlnvF+nY YqMVjXapb/PR4qE64a4fflXe+Pp12TCWgidnOe6RVox2c9GOU8/qKsg0H6zkQXvqcUGf nKr0IIUE+G4lcxLjJwBkm9KiuXvOGZsMnk5bnQ0+sEgauIrw8Ap62w9abMohAzgmWNzQ YAik0QeuL+buG1Yx69iN+mReQPKeTODzNGO89mMPmrEYz7uP2SwmepKibD9IAtPHTsX6 eUsQ== X-Gm-Message-State: AOAM533e7Z7fap6PehLqhyMbTYXh+wdy4Fk8Qb/1fE9BTtPBZgGTA4G8 3ZS1R+uLZp2GdnqbXAq69nOIq/TJsPtOdn5r3xM= X-Google-Smtp-Source: ABdhPJxZ1eF3+dItr//+AOLnCjl1xK4MAbDBZuwTXmCXlydwDA8h3zKcbEq+uVNW9CHV31hCF6fjoMcRYkqHpTmNQc4= X-Received: by 2002:a63:c00e:0:b0:398:a2b7:be6 with SMTP id h14-20020a63c00e000000b00398a2b70be6mr33238pgg.214.1650042405414; Fri, 15 Apr 2022 10:06:45 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Mir Immad Date: Fri, 15 Apr 2022 22:36:32 +0530 Message-ID: Subject: Re: GSoC proposal for extending static analyzer To: David Malcolm Cc: gcc@gcc.gnu.org X-Spam-Status: No, score=-0.1 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_INFOUSMEBIZ, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=no 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, 15 Apr 2022 17:06:49 -0000 I've updated the link on the repo -- https://mirimmad.github.io/zeta-lang. > You don't give many specifics in your personal decription. One thing > I'm not seeing is a sense of how proficient you are in various > programming languages. In particular, how is your C and C++? How > familiar are you with the debugger? Looking at your github, you seem > to have relevant experience in compilers, which is great, but all your > code appears to be with "managed" languages such as Ruby, Java, and > Python [and Zeta :)]. I'm pretty comfortable with both C and C++ and manual mem management . Unfortunately, I don't have any project in C/C++ to show. Maybe I can use the time before May 20 to write something in cpp? About the debugger, I'm okay-ish with it. In fact, it was due to the debugger (and your blog on it) that I was initially able to walk through the codebase. > That said, I got > the sense from your previous emails that you're not very familiar with > the APIs, and that you chose them because that was the suggestion I had > made on the wiki page. thats right. > Obviously it's something you can learn on the > way, but it would be better to accurately identify which areas you're > going need to learn along the way, and the timetable and scope should > reflect that. If I understand the statement correctly; currently I'm thinking of extending the support for open() (for creating the fd), write/read (for working on the fd) and close(). This is quite analogous to what we have in sm-file. Please let me know how do you want the analyzer to be extended and if you expect support for any other FD APIs too as I understand there are many other APIs for creating and working wiith FDs? Thank you. On Fri, Apr 15, 2022 at 9:35 PM David Malcolm wrote: > On Fri, 2022-04-15 at 19:58 +0530, Mir Immad wrote: > > I've submitted a proposal for extending the static analyzer to support > > posix fd APIs on GSoC website. Here is the Google docs link (gdocs > > < > > > https://docs.google.com/document/d/188zxPUsuYcF-uGVYL_G1s2RVtHhJSZeQ4sha40H7374/edit?usp=sharing > > >). > > > > > > Please take a look and let me know what you think. > > > > Thank you. > > Thanks. > > FWIW, I'm getting an error when trying the URL given in your github > repo: http://mirimmad.me/ > but https://mirimmad.github.io/ seems to work - but it's almost empty. > > You don't give many specifics in your personal decription. One thing > I'm not seeing is a sense of how proficient you are in various > programming languages. In particular, how is your C and C++? How > familiar are you with the debugger? Looking at your github, you seem > to have relevant experience in compilers, which is great, but all your > code appears to be with "managed" languages such as Ruby, Java, and > Python [and Zeta :)]. > > Also, the proposal is to extend the analyzer to cover a specific > domain: various POSIX APIs. Can you please give a sense of your level > of expertise with these APIs? I was pleased at your initiative in > trying to reuse the existing code to work with them. That said, I got > the sense from your previous emails that you're not very familiar with > the APIs, and that you chose them because that was the suggestion I had > made on the wiki page. Obviously it's something you can learn on the > way, but it would be better to accurately identify which areas you're > going need to learn along the way, and the timetable and scope should > reflect that. > > Hope this is constructive > Dave > > >