public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Malcolm <dmalcolm@redhat.com>
To: Mir Immad <mirimnan017@gmail.com>, gcc@gcc.gnu.org
Subject: Re: GSoC: Getting started
Date: Thu, 16 Jun 2022 11:27:24 -0400	[thread overview]
Message-ID: <389c81c69e3b8502fe832d0ac2b67d6f64d6fcb3.camel@redhat.com> (raw)
In-Reply-To: <69f2466b2bbcf360a027b8deff234dbc99df5348.camel@redhat.com>

On Wed, 2022-06-01 at 14:50 -0400, David Malcolm wrote:
> On Wed, 2022-06-01 at 23:22 +0530, Mir Immad wrote:
> > HI everyone,
> > 
> > I'm Immad Mir -- one of the GSoC students this year. I'll be working
> > on
> > adding static analysis support for POSIX file description APIs this
> > summer.
> 
> Welcome Immad - I'm looking forward to helping you on this project.
> 
> For reference, I think you posted an initial prototype of this work
> earlier this year here:
>   https://gcc.gnu.org/pipermail/gcc/2022-January/238192.html
>   https://gcc.gnu.org/pipermail/gcc/2022-February/238215.html
> 
> > 
> > The plan is to let the static analyzer know about the FD APIs through
> > the
> > use of function attributes, although initially we might hardcode the
> > logic
> > to get started working. I'm looking for the suggestions on this from
> > the
> > people who have experience working with file-descriptors.
> 
> We talked about this off-list; I think next steps could be:
> 
> (1) get your initial prototype working again, hardcoding the names of
> the functions for simplicity at first
> 
> (2) find a list of system calls (e.g. those implemented on Linux), and
> see which ones relate to file descriptors e.g. acquiring them, using
> them, releasing them, and duplicating them.  Look for patterns of usage
> that could be expressed using function attributes.  Probably ignore
> "ioctl" for now.
> 
> (3) probably talk to glibc's developers about this, since glibc
> provides headers that wrap system calls, which would want to use the
> attributes if we provide them
> 
> (4) implement the attributes, so that the analyzer doesn't have
> hardcoded function names, and can instead rely on function attributes.
> GCC's attributes are implemented in gcc/c-family/c-attribs.cc; see the
> big c_common_attribute_table array, which associates the string names
> of the attrbutes with properties, including a handler callback.  These
> either set flags of a decl, or the attribute itself is appended to a
> singly-linked list on that decl (for those things that don't directly
> relate to fields of a decl).
> 
> I believe Siddhesh Poyarekar has been looking at attributes from the
> glibc side of things, so I'm CCing him in case he has input on this.
> 
> I'm wondering if other people on this list have ideas for projects that
> make heavy use of syscalls/file-descriptors that would benefit from
> having this analyzer feature.  Maybe systemd?
> 
> Welcome again; hope this makes sense and is helpful
> Dave

I've gone ahead and filed an RFE bug in our bugzilla to help track this
work:
  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106003

Immad: you should probably assign that bug to yourself.  Do you have an
account yet for bugzilla?  See:
  https://gcc.gnu.org/gitwrite.html#authenticated
for info on how to get an account on sourceware.org/gcc.gnu.org

I can be your sponsor.

Once you have that, I think you automatically get a
USERNAME@gcc.gnu.org account that you can use to login to the GCC
bugzilla.


Dave


      parent reply	other threads:[~2022-06-16 15:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-01 17:52 Mir Immad
2022-06-01 18:50 ` David Malcolm
2022-06-07  3:43   ` Siddhesh Poyarekar
2022-06-16 15:27   ` David Malcolm [this message]

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=389c81c69e3b8502fe832d0ac2b67d6f64d6fcb3.camel@redhat.com \
    --to=dmalcolm@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=mirimnan017@gmail.com \
    /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).