Difference: CS255Spring09ProjectHome (28 vs. 29)

Revision 292009-03-22 - BinBao

Line: 1 to 1
 
META TOPICPARENT name="CS255Spring09"
Line: 113 to 113
 

Part 5: Group Competition

Changed:
<
<
By now you have a fairly complete grasp of the theories and techniques for redundancy elimination at the procedural level, working knowledge of the GCC compiler or URCC compiler, and a clear view of the optimization problem in terms of the type of the test programs. In the last phase of the project you have the freedom to develop creative and effective solutions and build your own super compiler. The results from the test programs and (later) hidden benchmarks will become part of the growing record of the annual compiler competition, so your compiler competes not only with the compiler from your classmates but also the best and brightest from the past years and future years. This is also the first time we can evaluate the GCC optimization passes using the same metric. You can beat current and future versions of GCC.
>
>
By now you have a fairly complete grasp of the theories and techniques for redundancy elimination at the procedural level, working knowledge of the GCC compiler or URCC compiler, and a clear view of the optimization problem in terms of the type of the test programs. In the last phase of the project you have the freedom to develop creative and effective solutions and build your own super compiler. The results from the test programs and (later) hidden benchmarks will become part of the growing record of the annual compiler competition, so your compiler competes not only with the compiler from your classmates but also the best and brightest from the past years and future years.
  The competition is organized in small teams, usually three or four students per team. We will ask you to fill out a Team-Project Questionnaire and organize teams and assign team leads based on your preference and our discretion. Undergrads are generally not treated differently unless we form a team with predominantly 255 students, in which case we will grade the team differently. Each member will be taking on one or more of the following roles:
Line: 136 to 136
 
  • Friday, March 27, design and implementation strategy reviewed.
  • Friday, April 3, first feedback from the hidden benchmarks.
  • Wednesday, April 8, second feedback from the hidden benchmarks.
Changed:
<
<
  • Monday, April 13, midnight, competition concludes.
>
>
  • Monday, April 13, 11:59pm, final code submission.
 

Competition Rules

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding URCS? Send feedback