Changes between Version 17 and Version 18 of GcnOperands

Timestamp:

06/06/17 12:00:29 (9 years ago)

Author:

trac

Comment:

--

GcnOperands

@@ -283 +283 @@
 (both  integer and floating points) and second is 32-bit immediate. Some type encoding
 allow to supply immediate with various size (16-bit or 12-bit).</p>
-<p>The literals are differently treated for scalar instructions and for vector instructions.
-In scalar instructions if operand is 64-bit, the literal value is exact value 64-bit value
-(sign or zero extended). By contrast, in vector instructions, for 64-bit operand, the
-literal is higher 32-bits of value (lower 32-bit are zero). Unhapilly, the CLRX assembler
-always encodes and decodes literal immediate as 32-bit value (except floating values).
+<p>The literals are differently treated for scalar/vector instructions and for
+double floating point operands in vector instructions.
+In scalar or vector instructions if operand is 64-bit, the literal value is exact value
+64-bit value (sign or zero extended). By contrast, in FP64 operands in vector instructions,
+for 64-bit operand, the literal is higher 32-bits of value (lower 32-bit are zero). Unhapilly, the CLRX assembler always encodes and decodes literal immediate as 32-bit
+value (except floating values).
 The immediate constants are always exact value, either for 32-bit and 64-bit operands.
 For example, instructions <code>v_frexp_exp_i32_f64 v3, lit(45)</code> and