Thank you. I will made it a little more specific.
And now I've made it a little bit slower ...
And divide my first stage work into 2 parts for the present.
I'll look for more information to accomplish it.
On Mon, Mar 17, 2014 at 3:26 AM, Joel Sherrill
<[email protected]> wrote:
>
> On Mar 16, 2014 2:15 PM, Ray Li <[email protected]> wrote:
>>
>> I have made a proposal and wonder if it is clearly and realistic?
>
> I am not a GCC mentor but have mentored for another project for 8 years. I
> would like to see more detail. For example, what exactly will you deliver by
> midterm? At the end?
>
> Break the effort into smaller steps so progress is easier to see and
> measure.
>
> A Go developer would have to answer this but I like to see something that
> shows a student is in a good place to start. Can you build GCC and Go and
> publish test results? Can you provide a small test case showing what is
> missing (assuming this is possible)?
>
> Will you need to do any copyright assignment paperwork? Ian will have to
> answer this.
>
> Break the project down, show you will hit the ground running, and show us
> how to measure your progress.
>
> --joel
> RTEMS and GCC
>
>>
>> Thanks for every correction.
>>
>> Ray
GCC Go escape analysis
The Project
The Project aims to accomplish escape analysis for gccgo.
Goal:
escape analysis
(optimization) converting heap allocation to stack allocation
Schedule:
21 April - 25 May
Preparation:communicate with mentor, read gccgo source code, get
familiar with tools, coding and documenting style, try submit some small
patches.
26 May - 8 June
Coding to implement GlobalEscape analysis.
9 June - 22 June
Coding to implement ArgEscape analysis
23 June - 29 June
finish mid-term evaluations
Do some tests and improvements.
30 June - 13 July
Some implementation work.(optimization: convert heap allocation
to stack allocation)
14 July - 11 August
(if permits)More optimization implementation.
Detailed Testing.
Details:
Mid-term: The basis implementation of escape analysis.(enable to
determine the 3 status of escape (GlobalEscape, ArgEscape and NoEscape))
Final results: Use escape analysis to do optimizations.(I have list
one, but I will try as fast to do more...)
