From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 82820 invoked by alias); 18 Jan 2018 23:10:46 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 82809 invoked by uid 89); 18 Jan 2018 23:10:45 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.0 required=5.0 tests=AWL,BAYES_00,KAM_LAZY_DOMAIN_SECURITY,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 spammy=Hx-languages-length:1030, summer X-HELO: mga05.intel.com Received: from mga05.intel.com (HELO mga05.intel.com) (192.55.52.43) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 18 Jan 2018 23:10:44 +0000 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Jan 2018 15:10:43 -0800 X-ExtLoop1: 1 Received: from tassilo.jf.intel.com (HELO tassilo.localdomain) ([10.7.201.35]) by fmsmga001.fm.intel.com with ESMTP; 18 Jan 2018 15:10:42 -0800 Received: by tassilo.localdomain (Postfix, from userid 1000) id 3084D300352; Thu, 18 Jan 2018 15:10:34 -0800 (PST) From: Andi Kleen To: Martin Jambor Cc: gcc@gcc.gnu.org, Jakub Jelinek , Martin Liska , "Joseph S. Myers" , David Edelsohn Subject: Re: Google Summer of Code 2018: Call for mentors and ideas References: Date: Thu, 18 Jan 2018 23:10:00 -0000 In-Reply-To: (Martin Jambor's message of "Wed, 17 Jan 2018 18:54:43 +0100") Message-ID: <874lniu5jp.fsf@linux.intel.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-SW-Source: 2018-01/txt/msg00128.txt.bz2 Martin Jambor 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