Out-of-order execution - Revision history

Jnc: Better cat

2018-12-15T14:04:23Z

Better cat

Jnc: better cat

2018-12-14T21:56:45Z

better cat

Jnc: +cat

2018-12-13T03:12:27Z

+cat

Jnc: clarify

2018-12-05T16:21:37Z

clarify

Jnc: An OK start

2018-12-05T02:21:36Z

An OK start

New page

'''Out-of-order execution''' (also called '''dynamic execution''') is a technique for improving the performance of a [[Central Processing Unit|processor]] by making use of what would otherwise be unused processor cycles. It does this by [[execute|executing]] [[instruction]]s in a different order than they appear in the [[object code]].

A certain amount of 'book-keeping' is required, to make sure that all the operands of a given instruction (especially including those calculated in previous instructions) are available, and that a location is available to store the results - the [[register renaming]] mechanism is used to handle that issue.

Out-of-order execution is common in [[superscalar]] machines which want to avoid the 'stalling' technique for dealing with conflicts.

It is a valuable technique because it means that [[software]] (both [[programmer]]s and [[compiler]]s) does not have to worry about execution order, etc; this is all dealt with by the hardware.

{{semi-stub}}

← Older revision		Revision as of 14:04, 15 December 2018
Line 9:		Line 9:
	{{semi-stub}}		{{semi-stub}}

−	[[Category: CPU ~~Basics‎‎~~]]	+	[[Category: CPU Hardware‎‎]]

← Older revision		Revision as of 21:56, 14 December 2018
Line 9:		Line 9:
	{{semi-stub}}		{{semi-stub}}

−	[[Category: ~~Hardware~~ Basics‎‎]]	+	[[Category: CPU Basics‎‎]]

← Older revision		Revision as of 03:12, 13 December 2018
Line 8:		Line 8:

	{{semi-stub}}		{{semi-stub}}
		+
		+	[[Category: Hardware Basics‎‎]]

@@ Line 5: / Line 5: @@
 Out-of-order execution is common in [[superscalar]] machines which want to avoid the 'stalling' technique for dealing with conflicts.
-It is a valuable technique because it means that [[software]] (both [[programmer]]s and [[compiler]]s) does not have to worry about execution order, etc; this is all dealt with by the hardware.
+It is a valuable technique because it means that [[software]] (both [[programmer]]s and [[compiler]]s) does not have to worry about execution order, in order to obtain the maximum performance; this is all dealt with by the hardware.
 {{semi-stub}}