Does VMFLE.VV write an FP vector?
No. Each active element writes one bit to mask vd.
Write active FP comparison results to mask vd.
In V 1.0, active body elements write vs2[i] <= vs1[i] to vd.mask[i]. vm=0 uses v0.t; vm=1 is unmasked. NaNs produce 0.
Decode the OP-V encoding and execute lane-wise FP compare: each active lane evaluates vs2[i] <= vs1[i] and writes the Boolean result to the destination mask bit.
lane 0: 1 <= 0.5 -> mask=0
This lane follows the current-step highlight; the remaining lane results appear below.
V-extension FP instructions use the OP-V major opcode, with funct6, source registers, vm, funct3, vd, and opcode fields.
The teaching context fixes VLEN=4096, LMUL=m1, vstart=0, valid vtype, enabled VS/FS, valid frm=RNE, and ta/ma, with the selected binary32/64 supported. Both vector sources have the same width; equal source registers require equal initial bits. vd is a single mask register, may be v0, and may start at a data source; legal different-EEW overlap forces mask/tail agnostic. Masked data sources cannot be v0 because one register cannot supply both EEW=1 mask and SEW data. Inactive bits have no definite displayed value; mask tails are always agnostic. VL=0 updates no destination bits. NV shows only what this execution raises and does not clear old fflags. Comparison does not round by frm, but invalid frm use remains reserved. Steps are not processor cycles.
SEW=32 / binary32 demo accepts finite values or full IEEE hexadecimal bit patterns, so qNaN/sNaN can be checked. Active lanes write 0/1 destination mask bits and show this execution's fflags.NV when required. Officially, VMFEQ/VMFNE raise invalid only for signaling NaN inputs; VMFLT/VMFLE/VMFGT/VMFGE raise invalid for signaling or quiet NaN inputs; VMFNE writes 1 when either operand is NaN, while the other compares write 0.Active elements write (vs2[i] <= vs1[i]) to vd.mask[i].
vd is one mask register: element i produces bit i, independent of SEW/LMUL, rather than a vector of SEW-bit 0/1 elements.
[, v0.t] denotes the optional execution mask: omitted means vm=1 and included means vm=0. Only active elements compare and raise NV; inactive/tail bits are not guaranteed zero.
The mask destination may be v0. Different-EEW destination/source overlap must start at the source group's lowest register and forces ma/ta. Masked data sources cannot also be v0. The animation fixes m1, so vd may equal a data source.
Require V 1.0, valid vtype, enabled VS/FS, supported FP width, and valid frm. vl=0 or vstart≥vl updates no destination bits. The animation fixes vstart=0 and VLEN=4096; steps are not processor cycles.
Assume RV32/RV64 V 1.0, enabled VS/FS, valid e32,m1, VLEN≥128, vl=4, vstart=0, frm=RNE, ta/ma, and initialized sources; unmasked. v2=[1.5,-0,2,1.5], v4=[1.5,0,1.5,1.5] → v1.mask[0..3]=[1,1,0,1]; this execution raises no NV and does not clear old fflags. Tails are always agnostic.
Assume RV32/RV64 V 1.0, enabled VS/FS, valid e32,m1, VLEN≥128, vl=4, vstart=0, frm=RNE, ta/ma, and initialized sources; unmasked. v2=[1.5,-0,2,1.5], v4=[1.5,0,1.5,1.5] → v1.mask[0..3]=[1,1,0,1]; this execution raises no NV and does not clear old fflags. Tails are always agnostic.
No. Each active element writes one bit to mask vd.
Yes. Mask-producing compares may overwrite source mask v0.
Only active elements raise flags; ordered comparison raises NV for either qNaN or sNaN. Either NaN produces 0, and +0 compares equal to -0.