모두의 코드
MOVNTPD (Intel x86/64 assembly instruction)

작성일 : 2020-09-01 이 글은 560 번 읽혔습니다.

MOVNTPD

Store Packed Double-Precision Floating-Point Values Using Non-Temporal Hint

참고 사항

아래 표를 해석하는 방법은 x86-64 명령어 레퍼런스 읽는 법 글을 참조하시기 바랍니다.

Opcode/
Instruction

Op /
En

64/32
bit Mode
Support

CPUID
Feature
Flag

Description

66 0F 2B /r
MOVNTPD m128 xmm1

MR

V/V

SSE2

Move packed double-precision values in xmm1 to m128 using non-temporal hint.

VEX.128.66.0F.WIG 2B /r
VMOVNTPD m128 xmm1

MR

V/V

AVX

Move packed double-precision values in xmm1 to m128 using non-temporal hint.

VEX.256.66.0F.WIG 2B /r
VMOVNTPD m256 ymm1

MR

V/V

AVX

Move packed double-precision values in ymm1 to m256 using non-temporal hint.

EVEX.128.66.0F.W1 2B /r
VMOVNTPD m128 xmm1

FVM

V/V

AVX512VL
AVX512F

Move packed double-precision values in xmm1 to m128 using non-temporal hint.

EVEX.256.66.0F.W1 2B /r
VMOVNTPD m256 ymm1

FVM

V/V

AVX512VL
AVX512F

Move packed double-precision values in ymm1 to m256 using non-temporal hint.

EVEX.512.66.0F.W1 2B /r
VMOVNTPD m512 zmm1

FVM

V/V

AVX512F

Move packed double-precision values in zmm1 to m512 using non-temporal hint.

Instruction Operand Encoding\footnote{1}

Op/En

Operand 1

Operand 2

Operand 3

Operand 4

MR

ModRM:r/m (w)

ModRM:reg (r)

NA

NA

FVM

ModRM:r/m (w)

ModRM:reg (r)

NA

NA

Description

Moves the packed double-precision floating-point values in the source operand (second operand) to the destination operand (first operand) using a non-temporal hint to prevent caching of the data during the write to memory. The source operand is an XMM register, YMM register or ZMM register, which is assumed to contain packed double-precision, floating-pointing data. The destination operand is a 128-bit, 256-bit or 512-bit memory location. The memory operand must be aligned on a 16-byte (128-bit version), 32-byte (VEX.256 encoded version) or 64-byte (EVEX.512 encoded version) boundary otherwise a general-protection exception (#GP) will be generated.

The non-temporal hint is implemented by using a write combining (WC) memory type protocol when writing the data to memory. Using this protocol, the processor does not write the data into the cache hierarchy, nor does it fetch the corresponding cache line from memory into the cache hierarchy. The memory type of the region being written to can override the non-temporal hint, if the memory address specified for the non-temporal store is in an uncacheable (UC) or write protected (WP) memory region. For more information on non-temporal stores, see "Caching of Temporal vs. Non-Temporal Data" in Chapter 10 in the IA-32 Intel Architecture Software Developer's Manual, Volume 1.

Because the WC protocol uses a weakly-ordered memory consistency model, a fencing operation implemented with the SFENCE or MFENCE instruction should be used in conjunction with MOVNTPD instructions if multiple processors might use different memory types to read/write the destination memory locations.

Note: VEX.vvvv and EVEX.vvvv are reserved and must be 1111b, VEX.L must be 0; otherwise instructions will #UD.

Operation

VMOVNTPD (EVEX encoded versions)

VL = 128, 256, 512
DEST[VL-1:0] <-  SRC[VL-1:0]
DEST[MAX_VL-1:VL] <-  0

MOVNTPD (Legacy and VEX versions)

DEST <- SRC

Intel C/C++ Compiler Intrinsic Equivalent

VMOVNTPD void _mm512_stream_pd(double* p, __m512d a);
VMOVNTPD void _mm256_stream_pd(double* p, __m256d a);
MOVNTPD void _mm_stream_pd(double* p, __m128d a);

SIMD Floating-Point Exceptions

None

Other Exceptions

Non-EVEX-encoded instruction, see Exceptions Type1.SSE2;

EVEX-encoded instruction, see Exceptions Type E1NF.

#UD If VEX.vvvv != 1111B or EVEX.vvvv != 1111B.

첫 댓글을 달아주세요!
프로필 사진 없음
강좌에 관련 없이 궁금한 내용은 여기를 사용해주세요

    댓글을 불러오는 중입니다..