This is the mail archive of the
mailing list for the GCC project.
Re: What are open tasks about GIMPLE loop optimizations?
- From: Evgeniya Maenkova <evgeniya dot maenkova at gmail dot com>
- To: Manuel LÃpez-IbÃÃez <lopezibanez at gmail dot com>
- Cc: Ilya Palachev <i dot palachev at samsung dot com>, gcc Mailing List <gcc at gcc dot gnu dot org>
- Date: Wed, 20 Aug 2014 18:25:22 +0400
- Subject: Re: What are open tasks about GIMPLE loop optimizations?
- Authentication-results: sourceware.org; auth=none
- References: <CANVW7MNjQj8XyQgaXYq3CM5hgQTFujYFVsV0poe3WTfg9cMM_g at mail dot gmail dot com> <53F1E17A dot 1020906 at samsung dot com> <CAESRpQBBZdb1c3nWZwvpDn2yuQFZqNzZ0afHCWHacRv6r+NBrA at mail dot gmail dot com> <CAESRpQC--1_dH-jVj6ef=xW4rpWwOk92O2wAT5WZsiNxe0vGjA at mail dot gmail dot com>
Dear Manuel and Ilya.
Thank you very much for you advices.
I'll take it into consideration.
On Mon, Aug 18, 2014 at 3:46 PM, Manuel LÃpez-IbÃÃez
> The wiki also contains the following: https://gcc.gnu.org/wiki/LoopOptTasks
> Probably very outdated, but updating it might be a helpful learning
> experience. Don't be afraid to edit the wiki, we can always revert
> your changes ;-)
> On 18 August 2014 13:43, Manuel LÃpez-IbÃÃez <firstname.lastname@example.org> wrote:
>>> *From:* Evgeniya Maenkova <email@example.com>
>>> *Sent:* Friday, August 15, 2014 4:45PM
>>> *To:* firstname.lastname@example.org
>>> *Subject:* What are open tasks about GIMPLE loop optimizations?
>>> Dear GCC Developers,
>>> Nobody answers my question below, so perhaps something wrong with my email
>> Starting as a newbie in GCC requires a lot of self-motivation. The
>> general answer to your question is to try. If something is wrong or
>> not what the GCC devs want, don't worry they will tell you.
>> See also the general advice here on how to interact with the GCC
>> community: https://gcc.gnu.org/wiki/GCC_Research
>> I would say your email falls into: "too long", "too general", "not
>> specific question", "not aimed at anyone in particular". :-)
>> For newbie tasks, the Summer of Code page has many ideas, some of them
>> with specific contact persons: https://gcc.gnu.org/wiki/SummerOfCode
>> See also the links under "Getting Started with GCC Development" at
>> And also https://gcc.gnu.org/wiki/ImprovementProjects
>> I would suggest to start fixing bug in the areas that interest you. If
>> you search in GCC's bugzilla, there must be plenty of bugs about
>> anything you can imagine. Even if you don't fix it, analyzing it would
>> be already helpful for you (to learn how to debug GCC, modify it and
>> rebuild) and for us to save us time.
>> Once you get enough knowledge, you will also get ideas of what
>> features are actually missing or could be improved.