This is the mail archive of the
mailing list for the GCC project.
Re: GCC GSOC 2016
- From: David Edelsohn <dje dot gcc at gmail dot com>
- To: Joel Sherrill <joel dot sherrill at oarcorp dot com>, Tobias Burnus <burnus at net-b dot de>, Maxim Kuvyrkov <maxim dot kuvyrkov at linaro dot org>
- Cc: Manuel LÃpez-IbÃÃez <lopezibanez at gmail dot com>, Ayush Goel <ayushgoel1610 at gmail dot com>, GCC Development <gcc at gcc dot gnu dot org>
- Date: Thu, 3 Mar 2016 08:54:45 -0500
- Subject: Re: GCC GSOC 2016
- Authentication-results: sourceware.org; auth=none
- References: <B53F14A0-2557-4684-A318-A6F2EED8F663 at gmail dot com> <56D812A0 dot 50500 at gmail dot com> <BC748E89-23D5-410A-953D-B9D1E2384023 at oarcorp dot com>
Tobias and Maxim were the recent coordinators.
On Thu, Mar 3, 2016 at 8:47 AM, Joel Sherrill <email@example.com> wrote:
> I may have missed this comment but GCC wouldn't need to apply as it's own GSoC project. The GNU Project applied as an umbrella organization and was accepted. Any GCC activities would be under that. I don't know who the organization administrator is for the GNU Project but the loop needs to be closed so GCC is included.
> FWIW the RTEMS community had been interested in improvements to coverage reporting but we don't have the expertise to do it without someone knowledgeable from GCC. We do have requirements.
> On March 3, 2016 4:32:00 AM CST, "Manuel LÃpez-IbÃÃez" <firstname.lastname@example.org> wrote:
>>On 01/03/16 19:38, Ayush Goel wrote:
>>Things related to development of GCC are best discussed in gcc@ (not
>>developers actually read gcc-help). I'm moving this discussion here.
>>> I am interested in contributing to gcc for the gsoc 2016.
>>Unfortunately, it seems GCC did not apply to participate in GSoC 2016
>>deadline passed already:
>>It also seems we did not apply last year either (at least
>>https://gcc.gnu.org/wiki/SummerOfCode does not show any accepted
>>I think some of us would be interested in mentoring students if they
>>their preferred project [*] (thus, it is better to propose several
>>see if a mentor is interested than to try to find a mentor for your
>>However, applying to GSoC requires some paperwork and commitment
>>mentoring, and GCC is lacking developers and existing developers have
>>time to dedicate to this.
>>> One of the projects listed a few years back, âConverting different
>>program representations level of GCC back to the source codeâ seems
>>really interesting to me, and Iâd like to discuss the possible ways
>>this could be done. Who should I get into touch with?
>>> Iâve been doing research in extracting call graphs from binaries and
>>analysing them and therefore have gathered sufficient information about
>>Intermediate representations, compiler optimisations. And so feel I
>>might be a good match for the project
>>My advice to you or any other prospective GSoC student would be:
>>a) Start publicly working on GCC now:
>>b) Get familiar with GCC devs on your area of interest.
>>c) Convince them that a project of yours would be so useful and
>>that they better spent the time/effort to get GCC in the next GSoC.
>>d) Once GCC is accepted by GSoC, we get so very few applications that
>>with a reasonable project (specially if they already have a willing
>>almost guaranteed to be accepted.
>>I understand that the above is not ideal, much less useful for this
>>year, but I
>>don't have anything better to offer, sorry. You could also apply to
>>are participating in GSoC this year:
>>[*] Projects I would be willing to mentor:
>>* Replace libiberty with gnulib. See
>>* Anything here: https://gcc.gnu.org/wiki/Better_Diagnostics
>>* Kill TREE_LIST (https://gcc.gnu.org/wiki/Speedup_areas#Trees)
>>* Kill TREE_VECTOR
>>* Kill %qE (not pretty-printing of expressions)
>>* Kill implicit input_location
>>* Revive the gdb compile project
>>(https://sourceware.org/gdb/wiki/GCCCompileAndExecute), which seems