From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id 923AE3858CDB for ; Sun, 2 Apr 2023 23:41:34 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 923AE3858CDB Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1680478894; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=BH0P2eyiTfrTJOQMYgA3c9IZf1QCDqTQJez4sdsIbzY=; b=Rrq2m4kgxAvpyjQFhYhVncZ0e1MPaaskg7CvgjbQHGnylSSdSSfNXzf85hH7wPru89p3Uu KS75Ypb3FE5PuEHQBkvW0+gVsFsUKMbkDQPsjQmO41mf4w3OcaLpQNB1vBe0faPSPUnim8 iKfFOjD0GiiVUOLDdveuvy+VyoZMPQc= Received: from mail-qt1-f198.google.com (mail-qt1-f198.google.com [209.85.160.198]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-549-p4jtpVQCN5Sj0TjdQFvDxQ-1; Sun, 02 Apr 2023 19:41:33 -0400 X-MC-Unique: p4jtpVQCN5Sj0TjdQFvDxQ-1 Received: by mail-qt1-f198.google.com with SMTP id l13-20020a05622a174d00b003e4df699997so16527099qtk.20 for ; Sun, 02 Apr 2023 16:41:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680478892; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=BH0P2eyiTfrTJOQMYgA3c9IZf1QCDqTQJez4sdsIbzY=; b=l+GapvbRh2fUO8CL5qMQJ5/f1TX2G0DXfh0J5hKQhJE3gwZ9kEmsbCqANd/PnrEoXQ y+pmhYLrvySvqwjcRx4/5+Py5qAyJJ31OJ+NUOJxS/DZe5Utvu4h7DfOH6pP+P/tO13H mofDQ0coWaZcMGiA3eAGnkVGbmJK1e+CAwoWiErV9MxZw0VARQ4ZMsNCS+MmLxGrHiLc N0Sg6vUf1Z1+nwdTRnT9Hue6ecCuBynfWdSb6Q61zh1x1lAHpa4zB2cn6xQ5EVT0VjbU Kurg9n4efu2Z2bJSAeVGwsodlzqUqZ5swhSoTCgTHnRAQY6cw/oxn+XU8cC8sNFj1bje 2tBQ== X-Gm-Message-State: AAQBX9fyY0Ys/Fb/uVX44nswI8fyePfNBC+LA+2sQsjp+2h510zOUOQi kK3X1ug8pQE8n0M/qAYm/Bc6W4ZZmTK2VQKG7o/sNujNOl0WoKuvGWb57acwg1BF6iqLWvacTdD +nDBayV+E7rWURIA= X-Received: by 2002:ad4:5c6e:0:b0:5ac:239a:9200 with SMTP id i14-20020ad45c6e000000b005ac239a9200mr66702366qvh.9.1680478892268; Sun, 02 Apr 2023 16:41:32 -0700 (PDT) X-Google-Smtp-Source: AKy350a1WIp++Na2P1Z06cUjD7dz+5JGleSoRWzsL4qQIzbh5FxMcboCJucGyfzC4OeD4dk+6/8McQ== X-Received: by 2002:ad4:5c6e:0:b0:5ac:239a:9200 with SMTP id i14-20020ad45c6e000000b005ac239a9200mr66702349qvh.9.1680478891998; Sun, 02 Apr 2023 16:41:31 -0700 (PDT) Received: from t14s.localdomain (c-73-69-212-193.hsd1.nh.comcast.net. [73.69.212.193]) by smtp.gmail.com with ESMTPSA id mn7-20020a0562145ec700b005dd8b93459fsm2245515qvb.55.2023.04.02.16.41.31 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 02 Apr 2023 16:41:31 -0700 (PDT) Message-ID: <6c579c3dc35185f346cfc591aea2a15052d4eb7a.camel@redhat.com> Subject: Re: GSoC: want to take part in `Extend the static analysis pass for CPython Extension` From: David Malcolm To: Sun Steven , "gcc@gcc.gnu.org" Date: Sun, 02 Apr 2023 19:41:30 -0400 In-Reply-To: References: User-Agent: Evolution 3.44.4 (3.44.4-1.fc36) MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-5.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_SHORT,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2,SPF_HELO_NONE,SPF_NONE,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: On Sat, 2023-04-01 at 20:32 +0000, Sun Steven via Gcc wrote: > Hello, Hi! I just replied to your other email in the "[GSoC] Interest and initial proposal for project on reimplementing cpychecker as -fanalyzer plugin " thread. >=20 > I want to take part in this project. >=20 > b. Write a plugin to add checking for usage of the CPython API (e.g. > reference-counting); see > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D107646 >=20 >=20 > I know the deadline is arriving, but this idea just came to me now. Indeed; the deadline for submitting proposals to the official GSoC website is April 4 - 18:00 UTC (i.e. this coming Tuesday); see: https://developers.google.com/open-source/gsoc/timeline Google are very strict about that deadline. >=20 > Self-intro: > I am a fan of C++, and have expertise in writing low-latency codes. I > previously worked at a high-frequency trading company, mainly writing > C++ and Python on Linux. >=20 > Familiarity with GCC: > I get an overall idea of how the compiler works. I have debugged > several GCC c++ frontend bugs. (eg. 108218,=C2=A0 99686, 99019,...)=C2=A0 Thanks; I just took a look at those. > But I only checked the c++ frontend codes in detail, not the middle > or backend codes. I have the ability to work with large codebases. >=20 > Familiarity with CPython: > I use a lot of CPython. Recently, I am contributing to the CPython > interpreter on PEP 701 (mainly on the parser, which I am familiar > with) >=20 >=20 > I have always been wanting to contribute major changes to GCC, but > just don't know if that project exists. I understand how middle-end > works, but never really interact with the GIMPLE. This project allows > me to take a real look at how GCC's middle end works. Given your knowledge of both C++ and of CPython internals, this project sounds like a good way for you to get involved. >=20 > I want to know if anyone was already on this project. I would prefer > a large-sized object (350hrs). I see you've already posted to the thread Eric started. >=20 > If b. was already taken, I also accept a. and c.=C2=A0 I had to check the wiki page to see which ones (a) and (c) were;=20 (a) is "Add format-string support to -fanalyzer." (c) is "Add a checker for some API or project of interest to the contributor (e.g. the Linux kernel, a POSIX API that we're not yet checking, or something else), either as a plugin, or as part of the analyzer core for e.g. POSIX." Do you have specific ideas for (c)? (a) would make a great project, in that it's reasonably self-contained. Eric's proposal for (b) plans to eventually tackle it, but there's a huge amount of potential work in (b) already. > By the way, I don't really care about the GSoC. If we miss the > deadline, we can still push forward this project without the support > of GSoC, as long as I get coached. I'm keen on helping new GCC contributors, with or without GSoC. A good next step is to build GCC from source, and try hacking in a new warning. See: https://gcc-newbies-guide.readthedocs.io/en/latest/ But remember that the GSoC deadline is April 4 - 18:00 UTC (i.e. this coming Tuesday), so if you're going to apply, you need to act fast. Good luck Dave