flat assembler
Message board for the users of flat assembler.

Index > Main > Opcodes, Mnemonics, Clock ticks, cycles

Author
Thread Post new topic Reply to topic
Alexander



Joined: 22 Dec 2008
Posts: 40
Alexander
Hi,

a few years ago I found some good sites about each x86 related mnemonic, opcode and micro-opcode.

Where can I find a full list of opcodes, mnemonics etc and their clock ticks or cycles needed out there?

I mean for example a mov-instruction requires .. clock ticks or cycles on a 386 and on a 286 it requires .., on a Pentium it requires ... cycles.

Where can I find such a complete list?

Thanks in advance
Alexander Very Happy
Post 27 Jan 2009, 21:30
View user's profile Send private message Reply with quote
vid
Verbosity in development


Joined: 05 Sep 2003
Posts: 7105
Location: Slovakia
vid
It is not as simple as you think. I suggest you to look for Agner Fog's optimization manual(s)
Post 27 Jan 2009, 21:34
View user's profile Send private message Visit poster's website AIM Address MSN Messenger ICQ Number Reply with quote
revolution
When all else fails, read the source


Joined: 24 Aug 2004
Posts: 17352
Location: In your JS exploiting you and your system
revolution
Also read Intel's and AMD's optimisation manuals. Both of them are very good.
Post 27 Jan 2009, 21:43
View user's profile Send private message Visit poster's website Reply with quote
Alexander



Joined: 22 Dec 2008
Posts: 40
Alexander
vid wrote:
It is not as simple as you think. I suggest you to look for Agner Fog's optimization manual(s)


wow vid,
sounds hot! Cool

especially:

http://www.phatcode.net/articles.php?id=263
http://www.agner.org/optimize/

vid, any more cool insider suggestions?

Is it possible to get the cycles myself? Or how does anyone gets the cycles?

Thanks


Last edited by Alexander on 27 Jan 2009, 21:48; edited 1 time in total
Post 27 Jan 2009, 21:46
View user's profile Send private message Reply with quote
Alexander



Joined: 22 Dec 2008
Posts: 40
Alexander
revolution,

I've tried to read the Intel optimisation manuals but haven't found anything useful.

Are AMD's manuals better?
Post 27 Jan 2009, 21:48
View user's profile Send private message Reply with quote
LocoDelAssembly
Your code has a bug


Joined: 06 May 2005
Posts: 4633
Location: Argentina
LocoDelAssembly
Quote:

Are AMD's manuals better?

They come with "Appendix C Instruction Latencies". But read Agner to have an idea of how those timings must be interpreted because it is not simple as the pre-pentium era to calculate how much time a code block could take.
Post 27 Jan 2009, 22:07
View user's profile Send private message Reply with quote
revolution
When all else fails, read the source


Joined: 24 Aug 2004
Posts: 17352
Location: In your JS exploiting you and your system
revolution
Alexander wrote:
I've tried to read the Intel optimisation manuals but haven't found anything useful.

Are AMD's manuals better?
I wouldn't say they are better or worse. They cover some different aspects of optimising. AMD have more extensive examples to show some of the techniques. Intel like to focus more on the theory and mathematics behind things.

I am surprised you say you found nothing useful! There is a lot of good info in there if one is serious about all aspects of optimisation.
Post 27 Jan 2009, 22:14
View user's profile Send private message Visit poster's website Reply with quote
Alexander



Joined: 22 Dec 2008
Posts: 40
Alexander
LocoDelAssembly,

you say "appendix c" ... ok, then I shall have a look at it!
Post 27 Jan 2009, 22:20
View user's profile Send private message Reply with quote
Display posts from previous:
Post new topic Reply to topic

Jump to:  


< Last Thread | Next Thread >
Forum Rules:
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Copyright © 1999-2020, Tomasz Grysztar. Also on YouTube, Twitter.

Website powered by rwasa.