From c33f99fb054417d45176280708642a324e8d14c4 Mon Sep 17 00:00:00 2001 From: eopXD Date: Fri, 10 Nov 2023 16:43:01 -0800 Subject: [PATCH] Update wordings for programming note on uninitialized variables based on Roger's suggestion Signed-off-by: eop Chen --- doc/rvv-intrinsic-spec.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/rvv-intrinsic-spec.adoc b/doc/rvv-intrinsic-spec.adoc index 6d98296a3..318022962 100644 --- a/doc/rvv-intrinsic-spec.adoc +++ b/doc/rvv-intrinsic-spec.adoc @@ -626,9 +626,9 @@ unsigned __riscv_vlenb(); === Uninitialized variables with RVV types and `vundefined` -Object created in the declaration of an RVV type represents a scalable-sized object that corresponds to a memory address. The default values inside such uninitialized values, and also to variables being assigned to the `vundefined` intrinsics represent non-deterministic values. Users should be aware to not rely on the result of these values. +Variables created in the declaration of an RVV type represents a scalable-sized object that corresponds to a memory address. The default values inside such uninitialized variables, and also to variables being assigned to the `vundefined` intrinsics, represent non-deterministic values. Users should be aware to not rely on the result of these values. -For example, a `vxor` operation to two either uninitialized or `vundefined` call will not yield a zero. +For example, a `vxor` operation whose operands are either two uninitialized variables or two function calls to `vundefined` may not yield a zero. === Copying vector register group contents