Xref: utzoo unix-pc.general:7004 comp.sys.att:11323 alt.sources.wanted:758 comp.sources.wanted:14644 comp.lang.c:34942
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!bloom-beacon!deccrl!news.crl.dec.com!pa.dec.com!shlump.nac.dec.com!labc.enet.dec.com!wallis
From: wallis@labc.enet.dec.com (Barry L. Wallis)
Newsgroups: unix-pc.general,comp.sys.att,alt.sources.wanted,comp.sources.wanted,comp.lang.c
Subject: Re: What assembler code is generated by C instruction X?
Message-ID: <18549@shlump.nac.dec.com>
Date: 30 Dec 90 03:42:21 GMT
Sender: newsdaemon@shlump.nac.dec.com
Followup-To: unix-pc.general
Organization: Digital Equipment Corporation
Lines: 24


In article <1990Dec28.220115.15930@shibaya.lonestar.org>, afc@shibaya.lonestar.org (Augustine Cano) writes...
|> 
|>The next thing that comes to mind is a bare bones program whose whole purpose
|>is to use each C instruction/construct once, with function and/or variable
|>names such that the particular item can be quickly located in the (many)
|>lines of assembler generated.  This would make it relatively easy to
|>connect assembly code with the C instruction that generated it, for any
|>compiler/cpu type, without extraneous garbage in the way.
|> 

You may want to try using something like Borland's Turbo Debugger VIEW-CPU
window. This will show you each source line with the relevant assembler code
beneath it. You can dump this to the logwindow and write it to disk.

BTW, what are you planning to do about optimizations (e.g., the same source
line(s) may generate different code depending on other source lines).

---
Barry L. Wallis			USENET: wallis@labc.dec.com
Database Consultant		Prodigy (don't laugh): DNMX41A
U.S. DECtp Resource Center	DECUServe: EISNER::WALLIS (not on the net yet)
Los Angeles, CA			"No one voted for me, I represent myself"
---