From: Andi Kleen <ak@linux.intel.com>
To: Martin Jambor <mjambor@suse.cz>
Cc: gcc@gcc.gnu.org, Jakub Jelinek <jakub@redhat.com>,
Martin Liska <mliska@suse.cz>,
"Joseph S. Myers" <joseph@codesourcery.com>,
David Edelsohn <dje.gcc@gmail.com>
Subject: Re: Google Summer of Code 2018: Call for mentors and ideas
Date: Thu, 18 Jan 2018 23:10:00 -0000 [thread overview]
Message-ID: <874lniu5jp.fsf@linux.intel.com> (raw)
In-Reply-To: <ri6efmoxtek.fsf@suse.cz> (Martin Jambor's message of "Wed, 17 Jan 2018 18:54:43 +0100")
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
next prev parent reply other threads:[~2018-01-18 23:10 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 17:54 Martin Jambor
2018-01-17 21:06 ` Joseph Myers
2018-01-19 13:17 ` Martin Jambor
2018-01-19 16:34 ` Joseph Myers
2018-01-19 17:31 ` Richard Biener
2018-01-17 22:16 ` Joel Sherrill
2018-01-18 9:19 ` Martin Liška
2018-01-19 13:50 ` Martin Jambor
2018-01-18 9:41 ` Martin Liška
2018-01-19 14:09 ` Martin Jambor
2018-01-19 14:13 ` Martin Jambor
2018-01-22 15:10 ` Martin Liška
2018-01-22 15:40 ` Martin Liška
2018-01-18 19:51 ` Eric Gallager
2018-01-18 20:31 ` Joseph Myers
2018-01-19 14:17 ` Martin Jambor
2018-01-18 23:10 ` Andi Kleen [this message]
2018-01-19 14:24 ` Martin Jambor
2018-01-23 10:56 ` Martin Jambor
2018-01-23 11:08 ` Prathamesh Kulkarni
2018-01-23 15:49 ` Martin Liška
2018-01-23 23:11 ` Martin Jambor
2018-02-13 13:02 ` Martin Jambor
2018-02-14 22:10 ` Janus Weil
2018-02-15 9:20 ` Martin Jambor
2018-02-15 10:52 ` Christopher Dimech
2018-02-15 12:12 ` Janus Weil
2018-02-15 13:59 ` Martin Jambor
2018-03-29 15:37 ` Joseph Myers
2018-03-29 16:40 ` Joseph Myers
2018-03-29 17:07 ` Martin Jambor
2018-04-03 11:30 ` Peryt, Sebastian
2018-04-03 14:09 ` Martin Jambor
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=874lniu5jp.fsf@linux.intel.com \
--to=ak@linux.intel.com \
--cc=dje.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=mjambor@suse.cz \
--cc=mliska@suse.cz \
/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).