public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Nada Elsayed <nadaelsayed163@gmail.com>
To: gcc@gcc.gnu.org
Cc: David Malcolm <dmalcolm@redhat.com>, ef2648@columbia.edu
Subject: GSoC Timeline Review
Date: Wed, 27 Mar 2024 02:31:55 +0200	[thread overview]
Message-ID: <CAEqVN38rsE5KpufjDdxT3y9V6Bi9jnC_U_0s+nh4_Y0qJLj2BA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]

Greetings All,
Hope this email finds you well.
I am interested in "Extend the plugin to add checking for usage of the
CPython API" project. First of all, I built the library, and now I am
trying to debug it. Then, I also used Cpython in 3 demos to understand how
it works. Finally, I read the uploaded patch comments to understand the
codebase and file structure.

I was wondering if you could review my suggested timeline?
suggested Timeline:

   -

   May 1-26:
   -

      Explore Cython modules, emphasizing entry-points and bug
      identification.
      -

      Study analyzers, particularly cpy-analyzer, to enhance understanding.
      -

      Debug the codebase to grasp its structure and potential areas for
      improvement.
      -

      Focus investigation on "errors in GIL handling" and "tp_traverse
      errors".
      -

   Weeks 1-6:
   -

      Investigate GIL (Global Interpreter Lock) errors extensively.
      -

      Engage in discussions and develop viable solutions to address
      identified issues.



   -

   Weeks 7-12:
   -

      Gain insight into the functioning of the Garbage Collector.
      -

      Implement checks to mitigate traverse errors effectively.
      -

      Ensure robust error handling mechanisms are in place through thorough
      study and practical implementation.

             reply	other threads:[~2024-03-27  0:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27  0:31 Nada Elsayed [this message]
2024-03-30 11:54 ` Nada Elsayed
2024-04-02 14:06   ` David Malcolm
2024-04-02 14:09     ` David Malcolm
2024-04-02 14:35 Martin Jambor
2024-04-04  2:38 ` Eric Feng

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=CAEqVN38rsE5KpufjDdxT3y9V6Bi9jnC_U_0s+nh4_Y0qJLj2BA@mail.gmail.com \
    --to=nadaelsayed163@gmail.com \
    --cc=dmalcolm@redhat.com \
    --cc=ef2648@columbia.edu \
    --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).