Author: Vincent Diepeveen
Date: 17:18:30 06/05/01
Go up one level in this thread
On June 05, 2001 at 20:09:38, Dann Corbit wrote:
>On June 05, 2001 at 19:58:38, Vincent Diepeveen wrote:
>>On June 05, 2001 at 14:04:42, Robert Hyatt wrote:
>[snip]
>>>What they see is what they will do. I think it better to show how it
>>>_should_ be done, as opposed to teaching bad habits by showing how it
>>>could be done more concisely.
>>
>>I'm not here to reveal code of mine. All programs here get 2 times
>>faster suddenly :)
>
>Aye. There's the rub. ;-)
>
>How about a hint?
Get a PDF on how the processor works. How the P3 works
is roughly how all processors work for the coming couple of years.
64 bits processors are
a) too expensive to press, as they need a bigger size
as 32 bits processors
b) hard to clock high
c) need a new OS
d) porting 32 bits code to 64 bits is done within a week anyway.
If you know what the processors are doing very badly, then you know
what to avoid. There is this great command in msvc.
dumpbin /disasm move.obj
Compare that with your printed manual of that processor's PDF.
then write down how many clocks everything eats.
Then go back to the C design board but keep in mind that nothing
beats assembly. I'm in C. So we both are in the poor class that
even though we can get pretty fast compared to the poor JAVA guys,
all we can do is make C code that prints to the less worst assembly
code.
For some weird reason i hardly see assembly posted here :)
Best regards,
Vincent
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.