Re: Debugging of optimized code

Stefan Monnier <monnier@di.epfl.ch>
Fri, 3 Feb 1995 08:30:18 GMT

          From comp.compilers
Related articles
[19 earlier articles]
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)
Re: Debugging of optimized code bill@amber.ssd.csd.harris.com (1995-02-01)
Re: Debugging of optimized code monnier@di.epfl.ch (Stefan Monnier) (1995-02-03)
Re: Debugging of optimized code ali@N2.SP.CS.CMU.EDU (Ali-Reza Adl-Tabatabai) (1995-02-03)
Re: Debugging of optimized code bill@amber.ssd.csd.harris.com (1995-02-05)
| List of all articles for this month |
Newsgroups: comp.compilers
From: Stefan Monnier <monnier@di.epfl.ch>
Keywords: optimize, debug
Organization: Ecole Polytechnique Federale de Lausanne
References: 95-01-036 95-02-008
Date: Fri, 3 Feb 1995 08:30:18 GMT

Jim Balter <jqb@netcom.com> wrote:
] debuggable. As processors and compilers become faster, compilation speed
] becomes less of an issue. And optimizer bugs should be no different from


I'm not so sure. Processors might get faster, but they also get harder
to generate code for: I don't think average compile time has
noticeably decreased these last few years.


I expect a lot more from incremental compilation than from processor
speed improvements..




Stefan
--

Post a followup to this message

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