Related articles |
---|
Pushes, Pops, NOPS vbjohny@yahoo.com (2003-12-03) |
Re: Pushes, Pops, NOPS Barak.Zalstein@ParthusCeva.com (Barak Zalstein) (2003-12-08) |
Re: Pushes, Pops, NOPS tmk@netvision.net.il (2003-12-08) |
Re: Pushes, Pops, NOPS nick.roberts@acm.org (Nick Roberts) (2003-12-08) |
Re: Pushes, Pops, NOPS kenrose@tfb.com (Ken Rose) (2003-12-08) |
Re: Pushes, Pops, NOPS vbdis@aol.com (2003-12-08) |
Re: Pushes, Pops, NOPS lex@cc.gatech.edu (Lex Spoon) (2003-12-13) |
From: | vbdis@aol.com (VBDis) |
Newsgroups: | comp.compilers |
Date: | 8 Dec 2003 00:28:32 -0500 |
Organization: | AOL Bertelsmann Online GmbH & Co. KG http://www.germany.aol.com |
References: | 03-12-032 |
Keywords: | code, optimize |
Posted-Date: | 08 Dec 2003 00:28:32 EST |
vbjohny@yahoo.com (Kalyan) schreibt:
>Could anyone please tell me if there are any freeware
>or shareware assembler or compiler tools that would eliminate these
>unnecessary instructions?
IMO a simple script would allow to remove NOPs and superfluous PUSH/POP
sequences from the assembler source. A good compiler wouldn't produce such
(sequences of) instructions at all; what's the reason why you have to edit the
assembly code manually? And why insert NOPs, are you paid by code lines? <gd&r>
DoDi
Return to the
comp.compilers page.
Search the
comp.compilers archives again.