Return to the
comp.compilers page.
Search the
comp.compilers archives again.
| Related articles |
|---|
| EQNTOTT Vectors of 16 bit Numbers [Was: Re: Yikes!!! New 200Mhz Intel glew@ichips.intel.com (1995-11-09) |
| Re: EQNTOTT Vectors of 16 bit Numbers [Was: Re: Yikes!!! New 200Mhz In pardo@cs.washington.edu (1995-11-14) |
| Re: EQNTOTT Vectors of 16 bit Numbers hbaker@netcom.com (1995-11-19) |
| Re: EQNTOTT Vectors of 16 bit Numbers cliffc@ami.sps.mot.com (1995-11-20) |
| Re: EQNTOTT Vectors of 16 bit Numbers bernecky@eecg.toronto.edu (1995-11-20) |
| Re: EQNTOTT Vectors of 16 bit Numbers bernecky@eecg.toronto.edu (1995-11-21) |
| Newsgroups: | comp.sys.intel,comp.benchmarks,comp.compilers |
| From: | pardo@cs.washington.edu (David Keppel) |
| Keywords: | architecture, optimize, 586 |
| Organization: | Computer Science & Engineering, U. of Washington, Seattle |
| References: | <478ja4$6fu@nnrp3.news.primenet.com> <47j9hm$tdp@caesar.ultra.net> 95-11-079 |
| Date: | Tue, 14 Nov 1995 17:13:23 GMT |
>["Intel's special SPEC optimization."]
This reminds me of APL benchmarking from twenty years ago. The
interpreters recognized particular idioms and implemented them as
special cases. The APL vendors (notably, IBM) were accused of
"benchmark optimizations", though I think the original motivation
was speeding up real use.
Are byte/short optimizations useful on "Microsoft Word" applications?
I can't say for sure, but I've seen (and written) code that benefits
from coalescing memory and ALU operations, and that sometimes includes
irregular computations.
;-D on ( Vec Tour ) Pardo
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.