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: Martin Jambor <mjambor at suse dot cz>
- To: Andi Kleen <ak at linux dot intel dot com>
- Cc: gcc at gcc dot gnu dot org
- Cc:
- Date: Fri, 19 Jan 2018 15:24:41 +0100
- Subject: Re: Google Summer of Code 2018: Call for mentors and ideas
- Authentication-results: sourceware.org; auth=none
- References: <ri6efmoxtek.fsf@suse.cz> <874lniu5jp.fsf@linux.intel.com>
Hi Andi,
On Thu, Jan 18 2018, Andi Kleen wrote:
> 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.
>
Thanks a lot, project noted, it is an interesting idea. You are
definitely seasoned enough as far as I am concerned.
Martin