home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c
- Path: sparky!uunet!stanford.edu!CSD-NewsHost.Stanford.EDU!Xenon.Stanford.EDU!amorgan
- From: amorgan@Xenon.Stanford.EDU (Crunchy Frog)
- Subject: Re: Optimizing code for tests
- Message-ID: <1992Aug14.200553.3576@CSD-NewsHost.Stanford.EDU>
- Sender: news@CSD-NewsHost.Stanford.EDU
- Organization: Computer Science Department, Stanford University.
- References: <1992Aug12.200303.25050@tin.monsanto.com> <1992Aug14.192350.4786@tin.monsanto.com>
- Date: Fri, 14 Aug 1992 20:05:53 GMT
- Lines: 17
-
- In article <1992Aug14.192350.4786@tin.monsanto.com> bcschu@skws02.monsanto.com (Brett Schultz) writes:
- >
- >Many of you have also suggested to look for bottlenecks in my program.
- >I appreciate the info, but I have already found the bottlenecks and just
- >thought that optimized code runs faster than non-optimized code (esp. when
- >compiled with debugging info).
-
- Hold on, are you compiling with debugging on? Most compilers (GCC being
- one of the few exceptions) do not do optimization and debugging at the
- same time. Is this your problem?
-
- I am not sure what the -j option does, but if the manual says to
- use it, use it :-).
-
- >Brett
-
- C Frog
-