Related articles |
---|
[11 earlier articles] |
Re: Debugging of optimized code monnier@di.epfl.ch (Stefan Monnier) (1995-01-27) |
Re: Debugging of optimized code urs@engineering.ucsb.edu (1995-01-27) |
Re: Debugging of optimized code miker@metaware.com (1995-01-24) |
Re: Debugging of optimized code cef@geodesic.com (Charles Fiterman) (1995-01-25) |
Re: Debugging of optimized code danhicks@aol.com (1995-01-27) |
Re: Debugging of optimized code danhicks@aol.com (1995-01-29) |
Re: Debugging of optimized code monnier@di.epfl.ch (Stefan Monnier) (1995-01-27) |
Re: Debugging of optimized code jqb@netcom.com (1995-02-02) |
Debugging of optimized code ssimmons@convex.convex.com (1995-02-02) |
Re: Debugging of optimized code copperma@grenoble.rxrc.xerox.com (1995-01-30) |
Re: Debugging of optimized code wicklund@Intellistor.COM (1995-01-30) |
Re: Debugging of optimized code copperma@grenoble.rxrc.xerox.com (1995-01-30) |
Debugging of optimized code cliffc@hpl.hp.com (1995-02-02) |
[4 later articles] |
Newsgroups: | comp.compilers |
From: | Stefan Monnier <monnier@di.epfl.ch> |
Keywords: | debug, optimize |
Organization: | Ecole Polytechnique Federale de Lausanne |
References: | 95-01-036 95-01-082 |
Date: | Fri, 27 Jan 1995 09:07:39 GMT |
<sam@ccnet.com> wrote:
] I have found that just disabling register caching of variables
] accomplishes most of what you are looking for. The reason is, of
] course, that the "in memory" variables then reflect the real status
I guess the real reason is that basically no optimisations are
possible or useful any more once everything is in memory. The code
will probably end up being slower than the unoptimised version
(especially if the compiler allocates variables in registers even at
the lowest level of optimisation)...
Stefan
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.