Information on C++ programs

grunwald@foobar.cs.colorado.edu (Dirk Grunwald)
Tue, 15 Feb 1994 22:01:26 GMT

          From comp.compilers

Related articles
Information on C++ programs grunwald@foobar.cs.colorado.edu (1994-02-15)
| List of all articles for this month |

Newsgroups: comp.compilers,comp.lang.c++
From: grunwald@foobar.cs.colorado.edu (Dirk Grunwald)
Keywords: C++, report
Organization: University of Colorado at Boulder
Date: Tue, 15 Feb 1994 22:01:26 GMT

Recently, we completed a technical report that might be of interest to
comp.compilers and comp.lang.c++ readers.


``Quantifying Behavioral Differences Between C and C++ Programs''
by Brad Calder, Dirk Grunwald,and Benjamin Zorn
University of Colorado


The abstract follows. For copies of this paper, send mail to me
(grunwald@cs.colorado.edu) and I'll mail you a postscript copy of the
paper. Any comments on the paper are welcome and appreciated.n


Abstract:


Improving the performance of C programs has been a topic of great interest
for many years. Both hardware technology and compiler optimization
research has been applied in an effort to make C programs execute faster.
In many application domains, the C++ language is replacing C as the
programming language of choice. In this paper, we measure the empirical
behavior of a group of significant C and C++ programs and attempt to
identify and quantify behavioral differences between them. Our goal is to
determine whether optimization technology that has been successful for C
programs will also be successful in C++ programs. We furthermore identify
behavioral characteristics of C++ programs that suggest optimizations that
should be applied in those programs. Our results show that C++ programs
exhibit behavior that is significantly different than C programs. These
results should be of interest to compiler writers and architecture
designers who are designing systems to execute object-oriented programs.


Dirk Grunwald Asst. Prof, Univ. of Colorado at Boulder
--


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.