Re: Debugging of optimized code

I'm not sure if this is what you're looking for, but the SELF group
has done quite a bit of work on techniques for producing optimal code
that can be debugged. Their techiniques are a part of the larger set
of techiniques they have developed for producing optimal code for
their dynamic, prototype-based object-oriented language and
environment[SELF]. Instead of misstating the facts here, I direct you
to their www pages at http://self.stanford.edu/, where there are links
to papers; in particular, you might be interested in
    http://self.stanford.edu/papers/dynamic-deoptimization.html
which addresses this very issue in the context of SELF.


I'm not sure how interesting this will be to you, since it sounds like
you're talking about more traditional, statically typed, compiled
languages like C and Fortran in your post, but, in my experience,
anything that rings bells is likely to be useful at some point,
although I can't always see how.


-- Sean, who has just had to uglify his code twice in the last
two hours to get the compiler to stop optimizing away things
that are important for me to get a handle on in the debugger,
dangit!


--
sean levy, n-dim group, engineering design research center, carnegie mellon u.
snl+@cmu.edu +1412268{5215[vox],5229[fax]} 5000 forbes ave., pgh pa 15213, usa
                          http://paneer.ndim.edrc.cmu.edu:8888/~snl/Home.html
--

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