You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The vector facility for z/Architecture may be available on models implementing z/Architecture. When the facility is installed and enabled, vector instructions are available, having access to 32 128-bit registers.
The instructions are described in four chapters:
Chapter 21 describes the vector facility support instructions
Chapter 22 describes the vector facility integer instructions
Chapter 23 describes the vector facility string instructions
Chapter 24 describes the vector facility floating-point instructions.
Note: ESA/390 provided an optional vector facility, however this facility was never available on any processor capable of the z/Architecture architectural mode. The vector facility for z/Architecture differs from the ESA/390 vector facility in instruction and register definitions.
The text was updated successfully, but these errors were encountered:
Fish-Git
added
the
Missing
Support for the described architectural feature is currently missing and needs to be added.
label
Nov 29, 2017
Fish-Git
added
(*MOVED*)
(the original issue was moved into a different issue)
and removed
Missing
Support for the described architectural feature is currently missing and needs to be added.
labels
Dec 18, 2017
Vector Facility for z/Architecture (March, 2015)
The vector facility for z/Architecture may be available on models implementing z/Architecture. When the facility is installed and enabled, vector instructions are available, having access to 32 128-bit registers.
The instructions are described in four chapters:
Note: ESA/390 provided an optional vector facility, however this facility was never available on any processor capable of the z/Architecture architectural mode. The vector facility for z/Architecture differs from the ESA/390 vector facility in instruction and register definitions.
The text was updated successfully, but these errors were encountered: