CSiBE Benchmark

CSiBE Benchmark: One Year Perspective and PlansÁrpád Beszédes, Rudolf Ferenc, Tamás Gergely,Tibor Gyimóthy, Gábor Lóki, and László VidácsDepartment of Software EngineeringUniversity of Szeged, Hungary{beszedes,ferenc,gertom,gyimi,loki,lac}@inf.u szeged.huAbstract to produce compact code. Compilers are gen erally able to optimize for code speed or codesize. However, performance has been more ex In this paper we summarize our experiences intensively investigated and little effort has beendesigning and running CSiBE, the new codemade on optimizing for code size. This is truesize benchmark for GCC. Since its introduc for GCC as well; the majority of the compiler’stion in 2003, it has been widely used by GCCdevelopers are interested in the performance ofdevelopers in their daily work to help themthe generated code, not its size. Therefore op keep the size of the generated code as smalltimizations for space and the (side) effects ofas possible. We have been making continu modifications regarding code size are often ne ous observations on the latest results and in glected.forming GCC developers of any problem whennecessary. We overview some concrete “suc At the first GCC summit in 2003, we presentedcess stories” of where GCC benefited from our work related to the measurement of thethe benchmark. This paper overviews the code size generated by GCC [1]. We comparedmeasurement methodology, providing some in the size of the generated code to two non freeformation ...