| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Optimisation |
MB> > From a machine level point of view, you want branches to be not taken > more frequently than taken. This is because taking a branch > always flushes the prefetch instruction queue in the Intel > processors, [...] MB> With speculative execution and branch prediction in processors like the Pentium Pro, or the Cyrix 5x86 and 6x86, I don't believe that this is as true as it used to be. I sense a style war approaching, which is a pity, since it isn't really a stylistic problem (at least, not to me -- as I said previously). MB> > Unless you are in a truly critical area of the code, it is my opinion > that the paramount issue is source readability. MB> Indeed, and again I think that it is nitpicking to say that one is more legible than the other. More complex examples, maybe. But the cases in question are pretty much self-evident either way. > JdeBP < ___ X MegaMail 2.10 #0: --- Maximus/2 3.01* Origin: DoNoR/2,Woking UK (44-1483-725167) (2:440/4) SEEN-BY: 50/99 54/99 270/101 620/243 625/160 711/401 413 430 934 712/311 407 SEEN-BY: 712/505 506 517 623 624 704 713/317 800/1 @PATH: 440/4 141/209 270/101 712/624 711/934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.