This is the mail archive of the
mailing list for the GCC project.
Re: GCC GSoC 2020: Call for mentors and project ideas
- From: JeanHeyd Meneide <phdofthehouse at gmail dot com>
- To: David Malcolm <dmalcolm at redhat dot com>
- Cc: Martin Liška <mliska at suse dot cz>, Martin Jambor <mjambor at suse dot cz>, GCC Mailing List <gcc at gcc dot gnu dot org>, Gfortran mailing list <fortran at gcc dot gnu dot org>, "libstdc++" <libstdc++ at gcc dot gnu dot org>
- Date: Thu, 13 Feb 2020 00:02:28 +0100
- Subject: Re: GCC GSoC 2020: Call for mentors and project ideas
- References: <firstname.lastname@example.org> <email@example.com> <firstname.lastname@example.org> <email@example.com>
Dear GCC Team,
A bit of a procedural question. Do applications/projects for glibc
apply here to GCC? There are a few core functions I would like to add to
the library, that I think would be beneficial. Would a proposal for that be
welcome to GCC, or is it headed by a different organization?
On Wed, Feb 12, 2020 at 11:55 PM David Malcolm <firstname.lastname@example.org> wrote:
> On Thu, 2020-02-06 at 20:58 -0500, David Malcolm wrote:
> > On Mon, 2020-01-27 at 16:30 +0100, Martin Liška wrote:
> > > On 1/15/20 11:45 PM, Martin Jambor wrote:
> > > > Therefore, first and foremost, I would like to ask all
> > > > (moderately)
> > > > seasoned GCC contributors to consider mentoring a student this
> > > > year
> > > > and
> > > > ideally also come up with a project that they would like to
> > > > lead. I'm
> > > > collecting proposal on our wiki page
> > >
> > > @David would you be interested in a analyzer topics? Seems to me
> > > ideal for newcomers to come up with a static analyzer check?
> > I'm not quite sure what the appropriate size of a project would be,
> > but
> > I'd be happy to mentor a student. Some ideas I had for analyzer
> > topics:
> > * Generalize double-free checker to attribute-marking of
> > acquire/release API entrypoints so that the user can mark the
> > entrypoints and get a checker for that API "for free".
> > * Checking of the POSIX file-descriptor APIs (int rather than FILE
> > *),
> > or some other POSIX API that we're not yet checking.
> > * Maybe add plugin support, and write a plugin to add a project
> > specific-checker for a project of interest to the student (Linux
> > kernel?)
> > * C++ support (new/delete checking, exceptions, etc)
> > Thoughts?
> > Dave
> I've taken the liberty of adding the above idea to the list of
> "Selected Project Ideas for 2020" on
> with me as mentor.