This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Google Summer of Code 2018: Call for mentors and ideas
- From: Andi Kleen <ak at linux dot intel dot com>
- To: Martin Jambor <mjambor at suse dot cz>
- Cc: gcc at gcc dot gnu dot org, Jakub Jelinek <jakub at redhat dot com>, Martin Liska <mliska at suse dot cz>, "Joseph S. Myers" <joseph at codesourcery dot com>, David Edelsohn <dje dot gcc at gmail dot com>
- Date: Thu, 18 Jan 2018 15:10:34 -0800
- Subject: Re: Google Summer of Code 2018: Call for mentors and ideas
- Authentication-results: sourceware.org; auth=none
- References: <ri6efmoxtek.fsf@suse.cz>
Martin Jambor <mjambor@suse.cz> writes:
>
> Therefore I would like to ask all seasoned GCC contributors who would
> like to mentor a GSoC student to send a reply to this thread with their
> idea for a project. If you have an idea but you do not want to be a
> mentor then I will consider it only if it is really interesting, really
> specific (e.g. improving -O2 -g *somehow* is not specific) and I would
> have to be reasonably confident I'd find a good mentor for it. So far I
> have the following ideas from the IRC discussion:
Here's an idea:
fuzzers like csmith are fairly good at finding compiler bugs. But they
only generate standard C, but no extensions. gcc has many extensions,
which are not covered. It would be good to extend a fuzzer like csmith
to fuzz extensions like OpenMP, __attributes__, vector
extensions, etc. Then run the fuzzer and report
compiler bugs.
I'm not a seasoned gcc contributor, but would be willing to mentor
such a project.
-Andi