Processor question

I read that, most of the time, jumps make the processor flush the pipeline,
or the cache, or the other cache, I suppose in order of severity (short /
near / far jump). What kind of preprocessing and caching strategies are
people mucking around with these days?

I thought of this question while contemplating QBasic. You see, even with
over 1.8GHz available today (I say 1.8 because that's only what I'm sitting
in front of now :) ), a simple "sit in the corner and count to a billion"
takes QBasic over a minute! In contrast, a "somewhat" more optimized loop
written in assembly does 2^32 in just seven seconds.

Tim

--
Deep Fryer: A very philosophical monk.
Website @ http://webpages.charter.net/dawill/tmoranwms


.

Relevant Pages

  • Re: Processor question
    ... pipeline, or the cache, or the other cache, I suppose in order of ... a program jumps all over but in a continuing and well-cached cycle, ... Thousands of different techniques for cache management, memory ... main memory is slow compared to cpu ...
    (sci.electronics.design)
  • Re: -Os versus -O2
    ... (even in the x86 family the costs of jumps, loops, and cache misses varies drasticly) ...
    (Linux-Kernel)
  • Re: Hyperthreading on 2.4.18 and 2.4.20 (Redhat)
    ... Hyperthread is just such an exotic idea! ... a stall on the pipeline / waste of executable units, ... cache lines are real. ... single thread is too much dependent on the scheduler. ...
    (comp.os.linux)
  • Re: Hyperthreading on 2.4.18 and 2.4.20 (Redhat)
    ... Hyperthread is just such an exotic idea! ... a stall on the pipeline / waste of executable units, ... cache lines are real. ... single thread is too much dependent on the scheduler. ...
    (alt.os.linux)
  • Re: Hyperthreading on 2.4.18 and 2.4.20 (Redhat)
    ... Hyperthread is just such an exotic idea! ... a stall on the pipeline / waste of executable units, ... cache lines are real. ... single thread is too much dependent on the scheduler. ...
    (alt.os.linux.redhat)