diff options
author | tyb0807 <sontuan.vu@arm.com> | 2022-01-18 19:24:11 +0000 |
---|---|---|
committer | tyb0807 <sontuan.vu@arm.com> | 2022-01-31 20:50:16 +0000 |
commit | 13660715e677919d9a89dc6a3a77532593c3c7f6 (patch) | |
tree | 8e9d0d998c9bd607f77be858356138e30b8bfb5c /flang/lib/Frontend/CompilerInvocation.cpp | |
parent | 51e188d079f6ee9d8bc640351f2f772234d809dd (diff) | |
download | llvm-13660715e677919d9a89dc6a3a77532593c3c7f6.zip llvm-13660715e677919d9a89dc6a3a77532593c3c7f6.tar.gz llvm-13660715e677919d9a89dc6a3a77532593c3c7f6.tar.bz2 |
[AArch64] Modeling NZCV read/write for MOPS instructions
According to the specification, MOPS instructions define/use NZCV flags as
part of their semantics (see discussion in
https://reviews.llvm.org/D116157).
More specifically, the specification of the MOPS extension states that
each memcpy/memset/memmov operation will be performed by a series
of three MOPS instructions P, M and E. The P instruction writes to the
NZCV flags, while the others (M and E) reads from the NZCV flags.
This is part 2/4 of a series of patches split from
https://reviews.llvm.org/D117405 to facilitate reviewing.
Differential Revision: https://reviews.llvm.org/D117757
Diffstat (limited to 'flang/lib/Frontend/CompilerInvocation.cpp')
0 files changed, 0 insertions, 0 deletions