From: Robert Hoehne Newsgroups: comp.os.msdos.djgpp Subject: Re: RHIDE and gcc -S ??? Date: Tue, 03 Dec 1996 12:32:40 +0100 Organization: TU Chemnitz-Zwickau Lines: 43 Message-ID: <32A40FD8.C07@Mathematik.tu-chemnitz.de> References: <1 DOT 5 DOT 4 DOT 16 DOT 19960930231732 DOT 237f29e6 AT eelab DOT newpaltz DOT edu> NNTP-Posting-Host: process.hrz.tu-chemnitz.de Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: John Fortin DJ-Gateway: from newsgroup comp.os.msdos.djgpp John Fortin wrote: > > I wanted to compile a very short function and look at the > assembly created by gcc. It works fine in straight DOS At first: Please put in your posts also the exact version of RHIDE you are using, because this is very important for me. But in you case this is a common problem. You are right, if you say, that the commandline gcc -S foo.c works. But RHIDE gives gcc on the commandline evry time also the output filename and when you give within RHIDE the '-S' switch, gcc will be called like: gcc -c -S foo.c -o foo.o Which means, the assembler output is now in 'foo.o'. But there is also an other solution for your problem. If you add in RHIDE (or also on commandline) the '-save-temps' switch, then your program will be compiled normal and in addition gcc will put there also all the temp files whil creating the object file. Example: gcc -save-temps -c foo.c whill create (if successfull): foo.o - the object file foo.i - the preprocessed file foo.s - the assembler output file produced by cc1 Robert -- ***************************************************************** * Robert Hoehne, Fakultaet fuer Mathematik, TU-Chemnitz-Zwickau * * Post: Am Berg 3, D-09573 Dittmannsdorf * * e-Mail: Robert DOT Hoehne AT Mathematik DOT TU-Chemnitz DOT DE * * WWW: http://www.tu-chemnitz.de/~rho * *****************************************************************