Re: optimizing compiler against iaverage assembly programmer.

creedy@mitretek.org (Chris Reedy)
30 Jun 1997 23:09:27 -0400

          From comp.compilers

Related articles
[6 earlier articles]
Re: optimizing compiler against iaverage assembly programmer. jim-neil@digital.net (1997-06-24)
Re: optimizing compiler against iaverage assembly programmer. jbuck@synopsys.com (1997-06-24)
Re: optimizing compiler against iaverage assembly programmer. bromage@cs.mu.oz.au (1997-06-30)
Re: optimizing compiler against iaverage assembly programmer. charles.marslett@tempe.vlsi.com (1997-06-30)
Re: optimizing compiler against iaverage assembly programmer. graham.hughes@resnet.ucsb.edu (Graham C. Hughes) (1997-06-30)
Re: optimizing compiler against iaverage assembly programmer. WStreett@shell.monmouth.com (1997-06-30)
Re: optimizing compiler against iaverage assembly programmer. creedy@mitretek.org (1997-06-30)
Re: optimizing compiler against iaverage assembly programmer. als@tusc.com.au (1997-07-04)
Re: optimizing compiler against iaverage assembly programmer. conway@mundook.cs.mu.OZ.AU (1997-07-04)
Re: optimizing compiler against iaverage assembly programmer. als@tusc.com.au (1997-07-04)
Re: optimizing compiler against iaverage assembly programmer. dietz@interaccess.com (1997-07-04)
Re: optimizing compiler against iaverage assembly programmer. cef@geodesic.com (Charles Fiterman) (1997-07-04)
Re: optimizing compiler against iaverage assembly programmer. johncl@online.no (1997-07-04)
| List of all articles for this month |

From: creedy@mitretek.org (Chris Reedy)
Newsgroups: comp.compilers,comp.lang.asm.x86
Date: 30 Jun 1997 23:09:27 -0400
Organization: Mitretek Systems
References: 97-06-071 97-06-078 97-06-108
Keywords: assembler, optimize

bromage@cs.mu.oz.au (Andrew Bromage) wrote:
>
> Most programs that I write are not CPU-bound anyway. Either they are
> structure-crunching programs for which main memory is the bottleneck,
> disk-crunching programs for which I/O is the bottleneck, or interactive
> programs where most time is spent waiting for the human even with
> optimisation turned off. ...


I know of one interesting example - AI based game players (e.g. chess,
checkers, go, ...) - CPU intensive due to the searching. Also, as
someone who experiments with these in my spare time, I want the
compiler to generate good code since I change algorithms too often to
engage in hot spot improvements in assembly language.


    Chris


Dr. Christopher L. Reedy, Mail Stop Z667
Mitretek Systems, 7525 Colshire Drive, McLean, VA 22102-7400
Email: creedy@mitretek.org Phone: (703) 610-1615 FAX: (703) 610-1603
--


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.