Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| [9 earlier articles] |
| Re: Optimizing Across && And || bill@amber.ssd.csd.harris.com (1995-02-28) |
| Re: Optimizing Across && And || ryg@summit.novell.com (1995-03-03) |
| Re: Optimizing Across && And || leichter@zodiac.rutgers.edu (1995-03-07) |
| Re: Optimizing Across && And || preston@tera.com (1995-03-08) |
| Re: Optimizing Across && And || pardo@cs.washington.edu (1995-03-13) |
| Re: Optimizing Across && And || chase@centerline.com (1995-03-14) |
| Re: Optimizing Across && And || jqb@netcom.com (1995-03-15) |
| Re: Optimizing Across && And || cdg@nullstone.com (1995-03-20) |
| Re: Optimizing Across && And || daniels@cse.ogi.edu (1995-03-21) |
| dead code elimination preston@tera.com (1995-03-23) |
| Re: Optimizing Across && And || bill@amber.ssd.hcsc.com (1995-04-03) |
| Newsgroups: | comp.compilers |
| From: | jqb@netcom.com (Jim Balter) |
| Keywords: | C, optimize |
| Organization: | NETCOM On-line Communication Services (408 261-4700 guest) |
| References: | 95-02-179 95-03-053 |
| Date: | Wed, 15 Mar 1995 06:31:37 GMT |
ryg@summit.novell.com writes:
[about dead code elimination]
Preston Briggs <preston@tera.com> wrote:
>Now, some people will argue that this sort of thing never comes up, or
>that no one would write such a thing, or whatever. While I think
>those arguments are bogus, [...]
What these people may be missing is that there is another side to dead code
detection, namely *notification*. It is true that properly written programs
shouldn't contain dead code. Therefore, presence of dead code indicates
a possible problem.
--
<J Q B>
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.