Agner`s CPU blog

Software optimization resources | E-mail subscription to this blog | www.agner.org

Flat ViewSearchListList MessageboardsHelp
Stop the instruction set war
Author: Agner Date: 2016-04-17 07:21
Ruslan wrote:
It seems it'd be quite OK to have a particular opcode mean one thing on a CPU supporting feature X and not Y, and another thing on a CPU supporting feature Y and not X if these features are from different vendors. Why the battle for opcode space then?
If features X and Y are both useful then somebody might want to support both on a later design. It is too expensive for the software industry to support different mutually incompatible microprocessors.
Reply To This MessagePrevious MessageNext Message
 
thread Stop the instruction set war new - Agner Fog - 2009-12-05
replythread Stop the instruction set war new - Agner Fog - 2009-12-06
last reply The instruction set war's effect on virtualization new - Yuhong Bao - 2009-12-28
reply Stop the instruction set war new - Agner Fog - 2009-12-15
replythread Stop the instruction set war new - Norman Yarvin - 2010-01-09
last replythread Stop the instruction set war new - Agner Fog - 2010-01-10
last replythread Stop the instruction set war new - bitRAKE - 2010-01-12
last replythread Stop the instruction set war new - Agner Fog - 2010-01-13
last reply Pentium Appendix H new - Yuhong Bao - 2010-02-10
replythread Stop the instruction set war new - Agner Fog - 2010-09-25
last reply Stop the instruction set war new - Agner - 2011-08-28
replythread Stop the instruction set war new - Ruslan - 2016-04-17
last reply Stop the instruction set war - Agner - 2016-04-17
last reply Stop the instruction set war new - Agner - 2020-11-01
 
Flat ViewSearchListList MessageboardsHelp