2017-04-24 06:08:17 +08:00
|
|
|
; NOTE: Assertions have been autogenerated by utils/update_llc_test_checks.py
|
2017-08-01 23:14:35 +08:00
|
|
|
; RUN: llc < %s -mtriple=x86_64-unknown-unknown -print-schedule -mcpu=x86-64 -mattr=+avx | FileCheck %s --check-prefix=CHECK --check-prefix=GENERIC
|
2017-04-24 06:08:17 +08:00
|
|
|
; RUN: llc < %s -mtriple=x86_64-unknown-unknown -print-schedule -mcpu=sandybridge | FileCheck %s --check-prefix=CHECK --check-prefix=SANDY
|
|
|
|
; RUN: llc < %s -mtriple=x86_64-unknown-unknown -print-schedule -mcpu=ivybridge | FileCheck %s --check-prefix=CHECK --check-prefix=SANDY
|
|
|
|
; RUN: llc < %s -mtriple=x86_64-unknown-unknown -print-schedule -mcpu=haswell | FileCheck %s --check-prefix=CHECK --check-prefix=HASWELL
|
2017-08-30 16:08:50 +08:00
|
|
|
; RUN: llc < %s -mtriple=x86_64-unknown-unknown -print-schedule -mcpu=skylake | FileCheck %s --check-prefix=CHECK --check-prefix=SKYLAKE
|
2017-04-24 06:08:17 +08:00
|
|
|
; RUN: llc < %s -mtriple=x86_64-unknown-unknown -print-schedule -mcpu=btver2 | FileCheck %s --check-prefix=CHECK --check-prefix=BTVER2
|
2017-04-24 22:26:30 +08:00
|
|
|
; RUN: llc < %s -mtriple=x86_64-unknown-unknown -print-schedule -mcpu=znver1 | FileCheck %s --check-prefix=CHECK --check-prefix=ZNVER1
|
2017-04-24 06:08:17 +08:00
|
|
|
|
|
|
|
define <4 x double> @test_addpd(<4 x double> %a0, <4 x double> %a1, <4 x double> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_addpd:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: vaddpd (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-LABEL: test_addpd:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vaddpd (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_addpd:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vaddpd (%rdi), %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_addpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
|
|
|
; SKYLAKE-NEXT: vaddpd (%rdi), %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-LABEL: test_addpd:
|
|
|
|
; BTVER2: # BB#0:
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
|
|
|
; BTVER2-NEXT: vaddpd (%rdi), %ymm0, %ymm0 # sched: [8:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_addpd:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; ZNVER1-NEXT: vaddpd (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 06:08:17 +08:00
|
|
|
%1 = fadd <4 x double> %a0, %a1
|
|
|
|
%2 = load <4 x double>, <4 x double> *%a2, align 32
|
|
|
|
%3 = fadd <4 x double> %1, %2
|
|
|
|
ret <4 x double> %3
|
|
|
|
}
|
|
|
|
|
|
|
|
define <8 x float> @test_addps(<8 x float> %a0, <8 x float> %a1, <8 x float> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_addps:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: vaddps (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-LABEL: test_addps:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vaddps (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_addps:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vaddps (%rdi), %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_addps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
|
|
|
; SKYLAKE-NEXT: vaddps (%rdi), %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-LABEL: test_addps:
|
|
|
|
; BTVER2: # BB#0:
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
|
|
|
; BTVER2-NEXT: vaddps (%rdi), %ymm0, %ymm0 # sched: [8:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_addps:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; ZNVER1-NEXT: vaddps (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 06:08:17 +08:00
|
|
|
%1 = fadd <8 x float> %a0, %a1
|
|
|
|
%2 = load <8 x float>, <8 x float> *%a2, align 32
|
|
|
|
%3 = fadd <8 x float> %1, %2
|
|
|
|
ret <8 x float> %3
|
|
|
|
}
|
|
|
|
|
|
|
|
define <4 x double> @test_addsubpd(<4 x double> %a0, <4 x double> %a1, <4 x double> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_addsubpd:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vaddsubpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: vaddsubpd (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-LABEL: test_addsubpd:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vaddsubpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vaddsubpd (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_addsubpd:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vaddsubpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vaddsubpd (%rdi), %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_addsubpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vaddsubpd %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
|
|
|
; SKYLAKE-NEXT: vaddsubpd (%rdi), %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-LABEL: test_addsubpd:
|
|
|
|
; BTVER2: # BB#0:
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddsubpd %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
|
|
|
; BTVER2-NEXT: vaddsubpd (%rdi), %ymm0, %ymm0 # sched: [8:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_addsubpd:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vaddsubpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; ZNVER1-NEXT: vaddsubpd (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 06:08:17 +08:00
|
|
|
%1 = call <4 x double> @llvm.x86.avx.addsub.pd.256(<4 x double> %a0, <4 x double> %a1)
|
|
|
|
%2 = load <4 x double>, <4 x double> *%a2, align 32
|
|
|
|
%3 = call <4 x double> @llvm.x86.avx.addsub.pd.256(<4 x double> %1, <4 x double> %2)
|
|
|
|
ret <4 x double> %3
|
|
|
|
}
|
|
|
|
declare <4 x double> @llvm.x86.avx.addsub.pd.256(<4 x double>, <4 x double>) nounwind readnone
|
|
|
|
|
|
|
|
define <8 x float> @test_addsubps(<8 x float> %a0, <8 x float> %a1, <8 x float> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_addsubps:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vaddsubps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: vaddsubps (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-LABEL: test_addsubps:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vaddsubps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vaddsubps (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_addsubps:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vaddsubps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vaddsubps (%rdi), %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_addsubps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vaddsubps %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
|
|
|
; SKYLAKE-NEXT: vaddsubps (%rdi), %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-LABEL: test_addsubps:
|
|
|
|
; BTVER2: # BB#0:
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddsubps %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
|
|
|
; BTVER2-NEXT: vaddsubps (%rdi), %ymm0, %ymm0 # sched: [8:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_addsubps:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vaddsubps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; ZNVER1-NEXT: vaddsubps (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 06:08:17 +08:00
|
|
|
%1 = call <8 x float> @llvm.x86.avx.addsub.ps.256(<8 x float> %a0, <8 x float> %a1)
|
|
|
|
%2 = load <8 x float>, <8 x float> *%a2, align 32
|
|
|
|
%3 = call <8 x float> @llvm.x86.avx.addsub.ps.256(<8 x float> %1, <8 x float> %2)
|
|
|
|
ret <8 x float> %3
|
|
|
|
}
|
|
|
|
declare <8 x float> @llvm.x86.avx.addsub.ps.256(<8 x float>, <8 x float>) nounwind readnone
|
|
|
|
|
|
|
|
define <4 x double> @test_andnotpd(<4 x double> %a0, <4 x double> %a1, <4 x double> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_andnotpd:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vandnpd %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: vandnpd (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
|
|
|
; GENERIC-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-LABEL: test_andnotpd:
|
|
|
|
; SANDY: # BB#0:
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vandnpd %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
|
|
|
; SANDY-NEXT: vandnpd (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_andnotpd:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vandnpd %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vandnpd (%rdi), %ymm0, %ymm0 # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; HASWELL-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_andnotpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vandnpd %ymm1, %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: vandnpd (%rdi), %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-LABEL: test_andnotpd:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vandnpd %ymm1, %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vandnpd (%rdi), %ymm0, %ymm0 # sched: [6:1.00]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_andnotpd:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vandnpd %ymm1, %ymm0, %ymm0 # sched: [1:0.25]
|
|
|
|
; ZNVER1-NEXT: vandnpd (%rdi), %ymm0, %ymm0 # sched: [8:0.50]
|
|
|
|
; ZNVER1-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 06:08:17 +08:00
|
|
|
%1 = bitcast <4 x double> %a0 to <4 x i64>
|
|
|
|
%2 = bitcast <4 x double> %a1 to <4 x i64>
|
|
|
|
%3 = xor <4 x i64> %1, <i64 -1, i64 -1, i64 -1, i64 -1>
|
|
|
|
%4 = and <4 x i64> %3, %2
|
|
|
|
%5 = load <4 x double>, <4 x double> *%a2, align 32
|
|
|
|
%6 = bitcast <4 x double> %5 to <4 x i64>
|
|
|
|
%7 = xor <4 x i64> %4, <i64 -1, i64 -1, i64 -1, i64 -1>
|
|
|
|
%8 = and <4 x i64> %6, %7
|
|
|
|
%9 = bitcast <4 x i64> %8 to <4 x double>
|
|
|
|
%10 = fadd <4 x double> %a1, %9
|
|
|
|
ret <4 x double> %10
|
|
|
|
}
|
|
|
|
|
|
|
|
define <8 x float> @test_andnotps(<8 x float> %a0, <8 x float> %a1, <8 x float> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_andnotps:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vandnps %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: vandnps (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
|
|
|
; GENERIC-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-LABEL: test_andnotps:
|
|
|
|
; SANDY: # BB#0:
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vandnps %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
|
|
|
; SANDY-NEXT: vandnps (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_andnotps:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vandnps %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vandnps (%rdi), %ymm0, %ymm0 # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; HASWELL-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_andnotps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vandnps %ymm1, %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: vandnps (%rdi), %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-LABEL: test_andnotps:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vandnps %ymm1, %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vandnps (%rdi), %ymm0, %ymm0 # sched: [6:1.00]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [3:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_andnotps:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vandnps %ymm1, %ymm0, %ymm0 # sched: [1:0.25]
|
|
|
|
; ZNVER1-NEXT: vandnps (%rdi), %ymm0, %ymm0 # sched: [8:0.50]
|
|
|
|
; ZNVER1-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 06:08:17 +08:00
|
|
|
%1 = bitcast <8 x float> %a0 to <4 x i64>
|
|
|
|
%2 = bitcast <8 x float> %a1 to <4 x i64>
|
|
|
|
%3 = xor <4 x i64> %1, <i64 -1, i64 -1, i64 -1, i64 -1>
|
|
|
|
%4 = and <4 x i64> %3, %2
|
|
|
|
%5 = load <8 x float>, <8 x float> *%a2, align 32
|
|
|
|
%6 = bitcast <8 x float> %5 to <4 x i64>
|
|
|
|
%7 = xor <4 x i64> %4, <i64 -1, i64 -1, i64 -1, i64 -1>
|
|
|
|
%8 = and <4 x i64> %6, %7
|
|
|
|
%9 = bitcast <4 x i64> %8 to <8 x float>
|
|
|
|
%10 = fadd <8 x float> %a1, %9
|
|
|
|
ret <8 x float> %10
|
|
|
|
}
|
|
|
|
|
|
|
|
define <4 x double> @test_andpd(<4 x double> %a0, <4 x double> %a1, <4 x double> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_andpd:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vandpd %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vandpd (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-LABEL: test_andpd:
|
|
|
|
; SANDY: # BB#0:
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vandpd %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vandpd (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_andpd:
|
|
|
|
; HASWELL: # BB#0:
|
2017-06-28 19:23:31 +08:00
|
|
|
; HASWELL-NEXT: vandpd %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vandpd (%rdi), %ymm0, %ymm0 # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; HASWELL-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_andpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vandpd %ymm1, %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: vandpd (%rdi), %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-LABEL: test_andpd:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vandpd %ymm1, %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vandpd (%rdi), %ymm0, %ymm0 # sched: [6:1.00]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_andpd:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vandpd %ymm1, %ymm0, %ymm0 # sched: [1:0.25]
|
|
|
|
; ZNVER1-NEXT: vandpd (%rdi), %ymm0, %ymm0 # sched: [8:0.50]
|
|
|
|
; ZNVER1-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 06:08:17 +08:00
|
|
|
%1 = bitcast <4 x double> %a0 to <4 x i64>
|
|
|
|
%2 = bitcast <4 x double> %a1 to <4 x i64>
|
|
|
|
%3 = and <4 x i64> %1, %2
|
|
|
|
%4 = load <4 x double>, <4 x double> *%a2, align 32
|
|
|
|
%5 = bitcast <4 x double> %4 to <4 x i64>
|
|
|
|
%6 = and <4 x i64> %3, %5
|
|
|
|
%7 = bitcast <4 x i64> %6 to <4 x double>
|
|
|
|
%8 = fadd <4 x double> %a1, %7
|
|
|
|
ret <4 x double> %8
|
|
|
|
}
|
|
|
|
|
|
|
|
define <8 x float> @test_andps(<8 x float> %a0, <8 x float> %a1, <8 x float> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_andps:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vandps %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vandps (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-LABEL: test_andps:
|
|
|
|
; SANDY: # BB#0:
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vandps %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vandps (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_andps:
|
|
|
|
; HASWELL: # BB#0:
|
2017-06-28 19:23:31 +08:00
|
|
|
; HASWELL-NEXT: vandps %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vandps (%rdi), %ymm0, %ymm0 # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; HASWELL-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_andps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vandps %ymm1, %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: vandps (%rdi), %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-LABEL: test_andps:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vandps %ymm1, %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vandps (%rdi), %ymm0, %ymm0 # sched: [6:1.00]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [3:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_andps:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vandps %ymm1, %ymm0, %ymm0 # sched: [1:0.25]
|
|
|
|
; ZNVER1-NEXT: vandps (%rdi), %ymm0, %ymm0 # sched: [8:0.50]
|
|
|
|
; ZNVER1-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 06:08:17 +08:00
|
|
|
%1 = bitcast <8 x float> %a0 to <4 x i64>
|
|
|
|
%2 = bitcast <8 x float> %a1 to <4 x i64>
|
|
|
|
%3 = and <4 x i64> %1, %2
|
|
|
|
%4 = load <8 x float>, <8 x float> *%a2, align 32
|
|
|
|
%5 = bitcast <8 x float> %4 to <4 x i64>
|
|
|
|
%6 = and <4 x i64> %3, %5
|
|
|
|
%7 = bitcast <4 x i64> %6 to <8 x float>
|
|
|
|
%8 = fadd <8 x float> %a1, %7
|
|
|
|
ret <8 x float> %8
|
|
|
|
}
|
|
|
|
|
2017-04-24 22:26:30 +08:00
|
|
|
define <4 x double> @test_blendpd(<4 x double> %a0, <4 x double> %a1, <4 x double> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_blendpd:
|
|
|
|
; GENERIC: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vblendpd {{.*#+}} ymm0 = ymm0[0],ymm1[1,2],ymm0[3] sched: [1:0.50]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vblendpd {{.*#+}} ymm0 = ymm0[0],mem[1,2],ymm0[3] sched: [8:0.50]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_blendpd:
|
|
|
|
; SANDY: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vblendpd {{.*#+}} ymm0 = ymm0[0],ymm1[1,2],ymm0[3] sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vblendpd {{.*#+}} ymm0 = ymm0[0],mem[1,2],ymm0[3] sched: [8:0.50]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_blendpd:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vblendpd {{.*#+}} ymm0 = ymm0[0],ymm1[1,2],ymm0[3] sched: [1:0.33]
|
|
|
|
; HASWELL-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vblendpd {{.*#+}} ymm0 = ymm0[0],mem[1,2],ymm0[3] sched: [1:0.50]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_blendpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vblendpd {{.*#+}} ymm0 = ymm0[0],ymm1[1,2],ymm0[3] sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: vblendpd {{.*#+}} ymm0 = ymm0[0],mem[1,2],ymm0[3] sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_blendpd:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vblendpd {{.*#+}} ymm0 = ymm0[0],ymm1[1,2],ymm0[3] sched: [1:0.50]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:2.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: vblendpd {{.*#+}} ymm0 = ymm0[0],mem[1,2],ymm0[3] sched: [6:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_blendpd:
|
|
|
|
; ZNVER1: # BB#0:
|
|
|
|
; ZNVER1-NEXT: vblendpd {{.*#+}} ymm0 = ymm0[0],ymm1[1,2],ymm0[3] sched: [1:0.50]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
|
|
|
; ZNVER1-NEXT: vblendpd {{.*#+}} ymm0 = ymm0[0],mem[1,2],ymm0[3] sched: [8:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = shufflevector <4 x double> %a0, <4 x double> %a1, <4 x i32> <i32 0, i32 5, i32 6, i32 3>
|
|
|
|
%2 = load <4 x double>, <4 x double> *%a2, align 32
|
|
|
|
%3 = fadd <4 x double> %a1, %1
|
|
|
|
%4 = shufflevector <4 x double> %3, <4 x double> %2, <4 x i32> <i32 0, i32 5, i32 6, i32 3>
|
|
|
|
ret <4 x double> %4
|
|
|
|
}
|
|
|
|
|
|
|
|
define <8 x float> @test_blendps(<8 x float> %a0, <8 x float> %a1, <8 x float> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_blendps:
|
|
|
|
; GENERIC: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vblendps {{.*#+}} ymm0 = ymm0[0],ymm1[1,2],ymm0[3,4,5,6,7] sched: [1:0.50]
|
|
|
|
; GENERIC-NEXT: vblendps {{.*#+}} ymm0 = ymm0[0,1],mem[2],ymm0[3],mem[4,5,6],ymm0[7] sched: [8:0.50]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_blendps:
|
|
|
|
; SANDY: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vblendps {{.*#+}} ymm0 = ymm0[0],ymm1[1,2],ymm0[3,4,5,6,7] sched: [1:0.50]
|
|
|
|
; SANDY-NEXT: vblendps {{.*#+}} ymm0 = ymm0[0,1],mem[2],ymm0[3],mem[4,5,6],ymm0[7] sched: [8:0.50]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_blendps:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vblendps {{.*#+}} ymm0 = ymm0[0],ymm1[1,2],ymm0[3,4,5,6,7] sched: [1:0.33]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vblendps {{.*#+}} ymm0 = ymm0[0,1],mem[2],ymm0[3],mem[4,5,6],ymm0[7] sched: [1:0.50]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_blendps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vblendps {{.*#+}} ymm0 = ymm0[0],ymm1[1,2],ymm0[3,4,5,6,7] sched: [1:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: vblendps {{.*#+}} ymm0 = ymm0[0,1],mem[2],ymm0[3],mem[4,5,6],ymm0[7] sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_blendps:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vblendps {{.*#+}} ymm0 = ymm0[0],ymm1[1,2],ymm0[3,4,5,6,7] sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vblendps {{.*#+}} ymm0 = ymm0[0,1],mem[2],ymm0[3],mem[4,5,6],ymm0[7] sched: [6:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_blendps:
|
|
|
|
; ZNVER1: # BB#0:
|
|
|
|
; ZNVER1-NEXT: vblendps {{.*#+}} ymm0 = ymm0[0],ymm1[1,2],ymm0[3,4,5,6,7] sched: [1:0.50]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vblendps {{.*#+}} ymm0 = ymm0[0,1],mem[2],ymm0[3],mem[4,5,6],ymm0[7] sched: [8:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = shufflevector <8 x float> %a0, <8 x float> %a1, <8 x i32> <i32 0, i32 9, i32 10, i32 3, i32 4, i32 5, i32 6, i32 7>
|
|
|
|
%2 = load <8 x float>, <8 x float> *%a2, align 32
|
|
|
|
%3 = shufflevector <8 x float> %1, <8 x float> %2, <8 x i32> <i32 0, i32 1, i32 10, i32 3, i32 12, i32 13, i32 14, i32 7>
|
|
|
|
ret <8 x float> %3
|
|
|
|
}
|
|
|
|
|
|
|
|
define <4 x double> @test_blendvpd(<4 x double> %a0, <4 x double> %a1, <4 x double> %a2, <4 x double> *%a3) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_blendvpd:
|
|
|
|
; GENERIC: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vblendvpd %ymm2, %ymm1, %ymm0, %ymm0 # sched: [2:1.00]
|
|
|
|
; GENERIC-NEXT: vblendvpd %ymm2, (%rdi), %ymm0, %ymm0 # sched: [9:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_blendvpd:
|
|
|
|
; SANDY: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vblendvpd %ymm2, %ymm1, %ymm0, %ymm0 # sched: [2:1.00]
|
|
|
|
; SANDY-NEXT: vblendvpd %ymm2, (%rdi), %ymm0, %ymm0 # sched: [9:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_blendvpd:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vblendvpd %ymm2, %ymm1, %ymm0, %ymm0 # sched: [2:2.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vblendvpd %ymm2, (%rdi), %ymm0, %ymm0 # sched: [2:2.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_blendvpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vblendvpd %ymm2, %ymm1, %ymm0, %ymm0 # sched: [2:0.67]
|
|
|
|
; SKYLAKE-NEXT: vblendvpd %ymm2, (%rdi), %ymm0, %ymm0 # sched: [2:0.67]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_blendvpd:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vblendvpd %ymm2, %ymm1, %ymm0, %ymm0 # sched: [2:1.00]
|
|
|
|
; BTVER2-NEXT: vblendvpd %ymm2, (%rdi), %ymm0, %ymm0 # sched: [7:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_blendvpd:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vblendvpd %ymm2, %ymm1, %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; ZNVER1-NEXT: vblendvpd %ymm2, (%rdi), %ymm0, %ymm0 # sched: [8:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call <4 x double> @llvm.x86.avx.blendv.pd.256(<4 x double> %a0, <4 x double> %a1, <4 x double> %a2)
|
|
|
|
%2 = load <4 x double>, <4 x double> *%a3, align 32
|
|
|
|
%3 = call <4 x double> @llvm.x86.avx.blendv.pd.256(<4 x double> %1, <4 x double> %2, <4 x double> %a2)
|
|
|
|
ret <4 x double> %3
|
|
|
|
}
|
|
|
|
declare <4 x double> @llvm.x86.avx.blendv.pd.256(<4 x double>, <4 x double>, <4 x double>) nounwind readnone
|
|
|
|
|
|
|
|
define <8 x float> @test_blendvps(<8 x float> %a0, <8 x float> %a1, <8 x float> %a2, <8 x float> *%a3) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_blendvps:
|
|
|
|
; GENERIC: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vblendvps %ymm2, %ymm1, %ymm0, %ymm0 # sched: [2:1.00]
|
|
|
|
; GENERIC-NEXT: vblendvps %ymm2, (%rdi), %ymm0, %ymm0 # sched: [9:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_blendvps:
|
|
|
|
; SANDY: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vblendvps %ymm2, %ymm1, %ymm0, %ymm0 # sched: [2:1.00]
|
|
|
|
; SANDY-NEXT: vblendvps %ymm2, (%rdi), %ymm0, %ymm0 # sched: [9:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_blendvps:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vblendvps %ymm2, %ymm1, %ymm0, %ymm0 # sched: [2:2.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vblendvps %ymm2, (%rdi), %ymm0, %ymm0 # sched: [2:2.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_blendvps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vblendvps %ymm2, %ymm1, %ymm0, %ymm0 # sched: [2:0.67]
|
|
|
|
; SKYLAKE-NEXT: vblendvps %ymm2, (%rdi), %ymm0, %ymm0 # sched: [2:0.67]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_blendvps:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vblendvps %ymm2, %ymm1, %ymm0, %ymm0 # sched: [2:1.00]
|
|
|
|
; BTVER2-NEXT: vblendvps %ymm2, (%rdi), %ymm0, %ymm0 # sched: [7:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_blendvps:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vblendvps %ymm2, %ymm1, %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; ZNVER1-NEXT: vblendvps %ymm2, (%rdi), %ymm0, %ymm0 # sched: [8:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call <8 x float> @llvm.x86.avx.blendv.ps.256(<8 x float> %a0, <8 x float> %a1, <8 x float> %a2)
|
|
|
|
%2 = load <8 x float>, <8 x float> *%a3, align 32
|
|
|
|
%3 = call <8 x float> @llvm.x86.avx.blendv.ps.256(<8 x float> %1, <8 x float> %2, <8 x float> %a2)
|
|
|
|
ret <8 x float> %3
|
|
|
|
}
|
|
|
|
declare <8 x float> @llvm.x86.avx.blendv.ps.256(<8 x float>, <8 x float>, <8 x float>) nounwind readnone
|
|
|
|
|
|
|
|
define <8 x float> @test_broadcastf128(<4 x float> *%a0) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_broadcastf128:
|
|
|
|
; GENERIC: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vbroadcastf128 {{.*#+}} ymm0 = mem[0,1,0,1] sched: [7:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_broadcastf128:
|
|
|
|
; SANDY: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vbroadcastf128 {{.*#+}} ymm0 = mem[0,1,0,1] sched: [7:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_broadcastf128:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vbroadcastf128 {{.*#+}} ymm0 = mem[0,1,0,1] sched: [1:0.50]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_broadcastf128:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vbroadcastf128 {{.*#+}} ymm0 = mem[0,1,0,1] sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_broadcastf128:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vbroadcastf128 {{.*#+}} ymm0 = mem[0,1,0,1] sched: [6:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_broadcastf128:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vbroadcastf128 {{.*#+}} ymm0 = mem[0,1,0,1] sched: [8:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = load <4 x float>, <4 x float> *%a0, align 32
|
|
|
|
%2 = shufflevector <4 x float> %1, <4 x float> undef, <8 x i32> <i32 0, i32 1, i32 2, i32 3, i32 0, i32 1, i32 2, i32 3>
|
|
|
|
ret <8 x float> %2
|
|
|
|
}
|
|
|
|
|
|
|
|
define <4 x double> @test_broadcastsd_ymm(double *%a0) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_broadcastsd_ymm:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vbroadcastsd (%rdi), %ymm0 # sched: [7:0.50]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_broadcastsd_ymm:
|
|
|
|
; SANDY: # BB#0:
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vbroadcastsd (%rdi), %ymm0 # sched: [7:0.50]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_broadcastsd_ymm:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vbroadcastsd (%rdi), %ymm0 # sched: [1:0.50]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_broadcastsd_ymm:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vbroadcastsd (%rdi), %ymm0 # sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_broadcastsd_ymm:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vbroadcastsd (%rdi), %ymm0 # sched: [6:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_broadcastsd_ymm:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vbroadcastsd (%rdi), %ymm0 # sched: [8:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = load double, double *%a0, align 8
|
|
|
|
%2 = insertelement <4 x double> undef, double %1, i32 0
|
|
|
|
%3 = shufflevector <4 x double> %2, <4 x double> undef, <4 x i32> zeroinitializer
|
|
|
|
ret <4 x double> %3
|
|
|
|
}
|
|
|
|
|
|
|
|
define <4 x float> @test_broadcastss(float *%a0) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_broadcastss:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vbroadcastss (%rdi), %xmm0 # sched: [6:0.50]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_broadcastss:
|
|
|
|
; SANDY: # BB#0:
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vbroadcastss (%rdi), %xmm0 # sched: [6:0.50]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_broadcastss:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vbroadcastss (%rdi), %xmm0 # sched: [1:0.50]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_broadcastss:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vbroadcastss (%rdi), %xmm0 # sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_broadcastss:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vbroadcastss (%rdi), %xmm0 # sched: [5:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_broadcastss:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vbroadcastss (%rdi), %xmm0 # sched: [8:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = load float, float *%a0, align 4
|
|
|
|
%2 = insertelement <4 x float> undef, float %1, i32 0
|
|
|
|
%3 = shufflevector <4 x float> %2, <4 x float> undef, <4 x i32> zeroinitializer
|
|
|
|
ret <4 x float> %3
|
|
|
|
}
|
|
|
|
|
|
|
|
define <8 x float> @test_broadcastss_ymm(float *%a0) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_broadcastss_ymm:
|
|
|
|
; GENERIC: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vbroadcastss (%rdi), %ymm0 # sched: [7:0.50]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_broadcastss_ymm:
|
|
|
|
; SANDY: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vbroadcastss (%rdi), %ymm0 # sched: [7:0.50]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_broadcastss_ymm:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vbroadcastss (%rdi), %ymm0 # sched: [1:0.50]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_broadcastss_ymm:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vbroadcastss (%rdi), %ymm0 # sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_broadcastss_ymm:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vbroadcastss (%rdi), %ymm0 # sched: [6:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_broadcastss_ymm:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vbroadcastss (%rdi), %ymm0 # sched: [8:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = load float, float *%a0, align 4
|
|
|
|
%2 = insertelement <8 x float> undef, float %1, i32 0
|
|
|
|
%3 = shufflevector <8 x float> %2, <8 x float> undef, <8 x i32> zeroinitializer
|
|
|
|
ret <8 x float> %3
|
|
|
|
}
|
|
|
|
|
|
|
|
define <4 x double> @test_cmppd(<4 x double> %a0, <4 x double> %a1, <4 x double> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_cmppd:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vcmpeqpd %ymm1, %ymm0, %ymm1 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: vcmpeqpd (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
|
|
|
; GENERIC-NEXT: vorpd %ymm0, %ymm1, %ymm0 # sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_cmppd:
|
|
|
|
; SANDY: # BB#0:
|
2017-06-28 19:23:31 +08:00
|
|
|
; SANDY-NEXT: vcmpeqpd %ymm1, %ymm0, %ymm1 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vcmpeqpd (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
|
|
|
; SANDY-NEXT: vorpd %ymm0, %ymm1, %ymm0 # sched: [1:1.00]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_cmppd:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vcmpeqpd %ymm1, %ymm0, %ymm1 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vcmpeqpd (%rdi), %ymm0, %ymm0 # sched: [3:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vorpd %ymm0, %ymm1, %ymm0 # sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_cmppd:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vcmpeqpd %ymm1, %ymm0, %ymm1 # sched: [4:0.33]
|
|
|
|
; SKYLAKE-NEXT: vcmpeqpd (%rdi), %ymm0, %ymm0 # sched: [4:0.50]
|
|
|
|
; SKYLAKE-NEXT: vorpd %ymm0, %ymm1, %ymm0 # sched: [1:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_cmppd:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vcmpeqpd %ymm1, %ymm0, %ymm1 # sched: [3:1.00]
|
|
|
|
; BTVER2-NEXT: vcmpeqpd (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
|
|
|
; BTVER2-NEXT: vorpd %ymm0, %ymm1, %ymm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_cmppd:
|
|
|
|
; ZNVER1: # BB#0:
|
|
|
|
; ZNVER1-NEXT: vcmpeqpd %ymm1, %ymm0, %ymm1 # sched: [3:1.00]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vcmpeqpd (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
|
|
|
; ZNVER1-NEXT: vorpd %ymm0, %ymm1, %ymm0 # sched: [1:0.25]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = fcmp oeq <4 x double> %a0, %a1
|
|
|
|
%2 = load <4 x double>, <4 x double> *%a2, align 32
|
|
|
|
%3 = fcmp oeq <4 x double> %a0, %2
|
|
|
|
%4 = sext <4 x i1> %1 to <4 x i64>
|
|
|
|
%5 = sext <4 x i1> %3 to <4 x i64>
|
|
|
|
%6 = or <4 x i64> %4, %5
|
|
|
|
%7 = bitcast <4 x i64> %6 to <4 x double>
|
|
|
|
ret <4 x double> %7
|
|
|
|
}
|
|
|
|
|
|
|
|
define <8 x float> @test_cmpps(<8 x float> %a0, <8 x float> %a1, <8 x float> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_cmpps:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vcmpeqps %ymm1, %ymm0, %ymm1 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: vcmpeqps (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
|
|
|
; GENERIC-NEXT: vorps %ymm0, %ymm1, %ymm0 # sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_cmpps:
|
|
|
|
; SANDY: # BB#0:
|
2017-06-28 19:23:31 +08:00
|
|
|
; SANDY-NEXT: vcmpeqps %ymm1, %ymm0, %ymm1 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vcmpeqps (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
|
|
|
; SANDY-NEXT: vorps %ymm0, %ymm1, %ymm0 # sched: [1:1.00]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_cmpps:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vcmpeqps %ymm1, %ymm0, %ymm1 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vcmpeqps (%rdi), %ymm0, %ymm0 # sched: [3:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vorps %ymm0, %ymm1, %ymm0 # sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_cmpps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vcmpeqps %ymm1, %ymm0, %ymm1 # sched: [4:0.33]
|
|
|
|
; SKYLAKE-NEXT: vcmpeqps (%rdi), %ymm0, %ymm0 # sched: [4:0.50]
|
|
|
|
; SKYLAKE-NEXT: vorps %ymm0, %ymm1, %ymm0 # sched: [1:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_cmpps:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vcmpeqps %ymm1, %ymm0, %ymm1 # sched: [3:1.00]
|
|
|
|
; BTVER2-NEXT: vcmpeqps (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
|
|
|
; BTVER2-NEXT: vorps %ymm0, %ymm1, %ymm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_cmpps:
|
|
|
|
; ZNVER1: # BB#0:
|
|
|
|
; ZNVER1-NEXT: vcmpeqps %ymm1, %ymm0, %ymm1 # sched: [3:1.00]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vcmpeqps (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
|
|
|
; ZNVER1-NEXT: vorps %ymm0, %ymm1, %ymm0 # sched: [1:0.25]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = fcmp oeq <8 x float> %a0, %a1
|
|
|
|
%2 = load <8 x float>, <8 x float> *%a2, align 32
|
|
|
|
%3 = fcmp oeq <8 x float> %a0, %2
|
|
|
|
%4 = sext <8 x i1> %1 to <8 x i32>
|
|
|
|
%5 = sext <8 x i1> %3 to <8 x i32>
|
|
|
|
%6 = or <8 x i32> %4, %5
|
|
|
|
%7 = bitcast <8 x i32> %6 to <8 x float>
|
|
|
|
ret <8 x float> %7
|
|
|
|
}
|
|
|
|
|
|
|
|
define <4 x double> @test_cvtdq2pd(<4 x i32> %a0, <4 x i32> *%a1) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_cvtdq2pd:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vcvtdq2pd %xmm0, %ymm0 # sched: [4:1.00]
|
|
|
|
; GENERIC-NEXT: vcvtdq2pd (%rdi), %ymm1 # sched: [10:1.00]
|
|
|
|
; GENERIC-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_cvtdq2pd:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vcvtdq2pd %xmm0, %ymm0 # sched: [4:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vcvtdq2pd (%rdi), %ymm1 # sched: [10:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_cvtdq2pd:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vcvtdq2pd %xmm0, %ymm0 # sched: [6:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vcvtdq2pd (%rdi), %ymm1 # sched: [6:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_cvtdq2pd:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vcvtdq2pd %xmm0, %ymm0 # sched: [7:1.00]
|
|
|
|
; SKYLAKE-NEXT: vcvtdq2pd (%rdi), %ymm1 # sched: [7:1.00]
|
|
|
|
; SKYLAKE-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_cvtdq2pd:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vcvtdq2pd (%rdi), %ymm1 # sched: [8:1.00]
|
|
|
|
; BTVER2-NEXT: vcvtdq2pd %xmm0, %ymm0 # sched: [3:1.00]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_cvtdq2pd:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vcvtdq2pd (%rdi), %ymm1 # sched: [12:1.00]
|
|
|
|
; ZNVER1-NEXT: vcvtdq2pd %xmm0, %ymm0 # sched: [5:1.00]
|
|
|
|
; ZNVER1-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = sitofp <4 x i32> %a0 to <4 x double>
|
|
|
|
%2 = load <4 x i32>, <4 x i32> *%a1, align 16
|
|
|
|
%3 = sitofp <4 x i32> %2 to <4 x double>
|
|
|
|
%4 = fadd <4 x double> %1, %3
|
|
|
|
ret <4 x double> %4
|
|
|
|
}
|
|
|
|
|
|
|
|
define <8 x float> @test_cvtdq2ps(<8 x i32> %a0, <8 x i32> *%a1) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_cvtdq2ps:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vcvtdq2ps %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-25 08:56:05 +08:00
|
|
|
; GENERIC-NEXT: vcvtdq2ps (%rdi), %ymm1 # sched: [10:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_cvtdq2ps:
|
|
|
|
; SANDY: # BB#0:
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vcvtdq2ps %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; SANDY-NEXT: vmovaps (%rdi), %xmm1 # sched: [6:0.50]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vinsertf128 $1, 16(%rdi), %ymm1, %ymm1 # sched: [7:0.50]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vcvtdq2ps %ymm1, %ymm1 # sched: [3:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_cvtdq2ps:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vcvtdq2ps %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; HASWELL-NEXT: vcvtdq2ps (%rdi), %ymm1 # sched: [3:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_cvtdq2ps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vcvtdq2ps %ymm0, %ymm0 # sched: [4:0.33]
|
|
|
|
; SKYLAKE-NEXT: vcvtdq2ps (%rdi), %ymm1 # sched: [4:0.50]
|
|
|
|
; SKYLAKE-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_cvtdq2ps:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vcvtdq2ps (%rdi), %ymm1 # sched: [8:1.00]
|
|
|
|
; BTVER2-NEXT: vcvtdq2ps %ymm0, %ymm0 # sched: [3:1.00]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_cvtdq2ps:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vcvtdq2ps (%rdi), %ymm1 # sched: [12:1.00]
|
|
|
|
; ZNVER1-NEXT: vcvtdq2ps %ymm0, %ymm0 # sched: [5:1.00]
|
|
|
|
; ZNVER1-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = sitofp <8 x i32> %a0 to <8 x float>
|
|
|
|
%2 = load <8 x i32>, <8 x i32> *%a1, align 16
|
|
|
|
%3 = sitofp <8 x i32> %2 to <8 x float>
|
|
|
|
%4 = fadd <8 x float> %1, %3
|
|
|
|
ret <8 x float> %4
|
|
|
|
}
|
|
|
|
|
|
|
|
define <8 x i32> @test_cvtpd2dq(<4 x double> %a0, <4 x double> *%a1) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_cvtpd2dq:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vcvttpd2dq %ymm0, %xmm0 # sched: [4:1.00]
|
|
|
|
; GENERIC-NEXT: vcvttpd2dqy (%rdi), %xmm1 # sched: [11:1.00]
|
|
|
|
; GENERIC-NEXT: vinsertf128 $1, %xmm1, %ymm0, %ymm0 # sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_cvtpd2dq:
|
|
|
|
; SANDY: # BB#0:
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vcvttpd2dq %ymm0, %xmm0 # sched: [4:1.00]
|
|
|
|
; SANDY-NEXT: vcvttpd2dqy (%rdi), %xmm1 # sched: [11:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vinsertf128 $1, %xmm1, %ymm0, %ymm0 # sched: [1:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_cvtpd2dq:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vcvttpd2dq %ymm0, %xmm0 # sched: [6:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vcvttpd2dqy (%rdi), %xmm1 # sched: [7:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vinsertf128 $1, %xmm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_cvtpd2dq:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vcvttpd2dq %ymm0, %xmm0 # sched: [7:1.00]
|
|
|
|
; SKYLAKE-NEXT: vcvttpd2dqy (%rdi), %xmm1 # sched: [8:1.00]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: vinsertf128 $1, %xmm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_cvtpd2dq:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vcvttpd2dqy (%rdi), %xmm1 # sched: [8:1.00]
|
|
|
|
; BTVER2-NEXT: vcvttpd2dq %ymm0, %xmm0 # sched: [3:1.00]
|
|
|
|
; BTVER2-NEXT: vinsertf128 $1, %xmm1, %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_cvtpd2dq:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vcvttpd2dqy (%rdi), %xmm1 # sched: [12:1.00]
|
|
|
|
; ZNVER1-NEXT: vcvttpd2dq %ymm0, %xmm0 # sched: [5:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vinsertf128 $1, %xmm1, %ymm0, %ymm0 # sched: [2:0.67]
|
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = fptosi <4 x double> %a0 to <4 x i32>
|
|
|
|
%2 = load <4 x double>, <4 x double> *%a1, align 32
|
|
|
|
%3 = fptosi <4 x double> %2 to <4 x i32>
|
|
|
|
%4 = shufflevector <4 x i32> %1, <4 x i32> %3, <8 x i32> <i32 0, i32 1, i32 2, i32 3, i32 4, i32 5, i32 6, i32 7>
|
|
|
|
ret <8 x i32> %4
|
|
|
|
}
|
|
|
|
|
|
|
|
define <8 x float> @test_cvtpd2ps(<4 x double> %a0, <4 x double> *%a1) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_cvtpd2ps:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vcvtpd2ps %ymm0, %xmm0 # sched: [4:1.00]
|
|
|
|
; GENERIC-NEXT: vcvtpd2psy (%rdi), %xmm1 # sched: [11:1.00]
|
|
|
|
; GENERIC-NEXT: vinsertf128 $1, %xmm1, %ymm0, %ymm0 # sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_cvtpd2ps:
|
|
|
|
; SANDY: # BB#0:
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vcvtpd2ps %ymm0, %xmm0 # sched: [4:1.00]
|
|
|
|
; SANDY-NEXT: vcvtpd2psy (%rdi), %xmm1 # sched: [11:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vinsertf128 $1, %xmm1, %ymm0, %ymm0 # sched: [1:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_cvtpd2ps:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vcvtpd2ps %ymm0, %xmm0 # sched: [6:1.00]
|
|
|
|
; HASWELL-NEXT: vcvtpd2psy (%rdi), %xmm1 # sched: [7:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vinsertf128 $1, %xmm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_cvtpd2ps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vcvtpd2ps %ymm0, %xmm0 # sched: [7:1.00]
|
|
|
|
; SKYLAKE-NEXT: vcvtpd2psy (%rdi), %xmm1 # sched: [8:1.00]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: vinsertf128 $1, %xmm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_cvtpd2ps:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vcvtpd2psy (%rdi), %xmm1 # sched: [8:1.00]
|
|
|
|
; BTVER2-NEXT: vcvtpd2ps %ymm0, %xmm0 # sched: [3:1.00]
|
|
|
|
; BTVER2-NEXT: vinsertf128 $1, %xmm1, %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_cvtpd2ps:
|
|
|
|
; ZNVER1: # BB#0:
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vcvtpd2psy (%rdi), %xmm1 # sched: [11:1.00]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vcvtpd2ps %ymm0, %xmm0 # sched: [5:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vinsertf128 $1, %xmm1, %ymm0, %ymm0 # sched: [2:0.67]
|
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = fptrunc <4 x double> %a0 to <4 x float>
|
|
|
|
%2 = load <4 x double>, <4 x double> *%a1, align 32
|
|
|
|
%3 = fptrunc <4 x double> %2 to <4 x float>
|
|
|
|
%4 = shufflevector <4 x float> %1, <4 x float> %3, <8 x i32> <i32 0, i32 1, i32 2, i32 3, i32 4, i32 5, i32 6, i32 7>
|
|
|
|
ret <8 x float> %4
|
|
|
|
}
|
|
|
|
|
|
|
|
define <8 x i32> @test_cvtps2dq(<8 x float> %a0, <8 x float> *%a1) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_cvtps2dq:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vcvttps2dq %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vcvttps2dq (%rdi), %ymm1 # sched: [10:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vorps %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_cvtps2dq:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vcvttps2dq %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vcvttps2dq (%rdi), %ymm1 # sched: [10:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vorps %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_cvtps2dq:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vcvttps2dq %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vcvttps2dq (%rdi), %ymm1 # sched: [3:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vorps %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_cvtps2dq:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vcvttps2dq %ymm0, %ymm0 # sched: [4:0.33]
|
|
|
|
; SKYLAKE-NEXT: vcvttps2dq (%rdi), %ymm1 # sched: [4:0.50]
|
|
|
|
; SKYLAKE-NEXT: vorps %ymm1, %ymm0, %ymm0 # sched: [1:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_cvtps2dq:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vcvttps2dq (%rdi), %ymm1 # sched: [8:1.00]
|
|
|
|
; BTVER2-NEXT: vcvttps2dq %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; BTVER2-NEXT: vorps %ymm1, %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_cvtps2dq:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vcvttps2dq (%rdi), %ymm1 # sched: [12:1.00]
|
|
|
|
; ZNVER1-NEXT: vcvttps2dq %ymm0, %ymm0 # sched: [5:1.00]
|
|
|
|
; ZNVER1-NEXT: vorps %ymm1, %ymm0, %ymm0 # sched: [1:0.25]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = fptosi <8 x float> %a0 to <8 x i32>
|
|
|
|
%2 = load <8 x float>, <8 x float> *%a1, align 32
|
|
|
|
%3 = fptosi <8 x float> %2 to <8 x i32>
|
|
|
|
%4 = or <8 x i32> %1, %3
|
|
|
|
ret <8 x i32> %4
|
|
|
|
}
|
|
|
|
|
2017-04-24 06:08:17 +08:00
|
|
|
define <4 x double> @test_divpd(<4 x double> %a0, <4 x double> %a1, <4 x double> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_divpd:
|
|
|
|
; GENERIC: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vdivpd %ymm1, %ymm0, %ymm0 # sched: [45:2.00]
|
|
|
|
; GENERIC-NEXT: vdivpd (%rdi), %ymm0, %ymm0 # sched: [52:2.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-LABEL: test_divpd:
|
|
|
|
; SANDY: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vdivpd %ymm1, %ymm0, %ymm0 # sched: [45:2.00]
|
|
|
|
; SANDY-NEXT: vdivpd (%rdi), %ymm0, %ymm0 # sched: [52:2.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_divpd:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vdivpd %ymm1, %ymm0, %ymm0 # sched: [35:2.00]
|
|
|
|
; HASWELL-NEXT: vdivpd (%rdi), %ymm0, %ymm0 # sched: [35:2.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_divpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vdivpd %ymm1, %ymm0, %ymm0 # sched: [14:1.00]
|
|
|
|
; SKYLAKE-NEXT: vdivpd (%rdi), %ymm0, %ymm0 # sched: [14:1.00]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-LABEL: test_divpd:
|
|
|
|
; BTVER2: # BB#0:
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vdivpd %ymm1, %ymm0, %ymm0 # sched: [38:38.00]
|
|
|
|
; BTVER2-NEXT: vdivpd (%rdi), %ymm0, %ymm0 # sched: [43:38.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_divpd:
|
|
|
|
; ZNVER1: # BB#0:
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vdivpd %ymm1, %ymm0, %ymm0 # sched: [15:15.00]
|
|
|
|
; ZNVER1-NEXT: vdivpd (%rdi), %ymm0, %ymm0 # sched: [22:22.00]
|
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 06:08:17 +08:00
|
|
|
%1 = fdiv <4 x double> %a0, %a1
|
|
|
|
%2 = load <4 x double>, <4 x double> *%a2, align 32
|
|
|
|
%3 = fdiv <4 x double> %1, %2
|
|
|
|
ret <4 x double> %3
|
|
|
|
}
|
|
|
|
|
|
|
|
define <8 x float> @test_divps(<8 x float> %a0, <8 x float> %a1, <8 x float> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_divps:
|
|
|
|
; GENERIC: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vdivps %ymm1, %ymm0, %ymm0 # sched: [29:2.00]
|
|
|
|
; GENERIC-NEXT: vdivps (%rdi), %ymm0, %ymm0 # sched: [36:2.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-LABEL: test_divps:
|
|
|
|
; SANDY: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vdivps %ymm1, %ymm0, %ymm0 # sched: [29:2.00]
|
|
|
|
; SANDY-NEXT: vdivps (%rdi), %ymm0, %ymm0 # sched: [36:2.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_divps:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vdivps %ymm1, %ymm0, %ymm0 # sched: [21:2.00]
|
|
|
|
; HASWELL-NEXT: vdivps (%rdi), %ymm0, %ymm0 # sched: [21:2.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_divps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vdivps %ymm1, %ymm0, %ymm0 # sched: [11:1.00]
|
|
|
|
; SKYLAKE-NEXT: vdivps (%rdi), %ymm0, %ymm0 # sched: [11:1.00]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-LABEL: test_divps:
|
|
|
|
; BTVER2: # BB#0:
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vdivps %ymm1, %ymm0, %ymm0 # sched: [38:38.00]
|
|
|
|
; BTVER2-NEXT: vdivps (%rdi), %ymm0, %ymm0 # sched: [43:38.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_divps:
|
|
|
|
; ZNVER1: # BB#0:
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vdivps %ymm1, %ymm0, %ymm0 # sched: [12:12.00]
|
|
|
|
; ZNVER1-NEXT: vdivps (%rdi), %ymm0, %ymm0 # sched: [19:19.00]
|
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 06:08:17 +08:00
|
|
|
%1 = fdiv <8 x float> %a0, %a1
|
|
|
|
%2 = load <8 x float>, <8 x float> *%a2, align 32
|
|
|
|
%3 = fdiv <8 x float> %1, %2
|
|
|
|
ret <8 x float> %3
|
|
|
|
}
|
|
|
|
|
2017-04-24 22:26:30 +08:00
|
|
|
define <8 x float> @test_dpps(<8 x float> %a0, <8 x float> %a1, <8 x float> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_dpps:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vdpps $7, %ymm1, %ymm0, %ymm0 # sched: [12:2.00]
|
|
|
|
; GENERIC-NEXT: vdpps $7, (%rdi), %ymm0, %ymm0 # sched: [7:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_dpps:
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY: # BB#0:
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vdpps $7, %ymm1, %ymm0, %ymm0 # sched: [12:2.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vdpps $7, (%rdi), %ymm0, %ymm0 # sched: [7:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-LABEL: test_dpps:
|
2017-04-24 06:08:17 +08:00
|
|
|
; HASWELL: # BB#0:
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vdpps $7, %ymm1, %ymm0, %ymm0 # sched: [14:2.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vdpps $7, (%rdi), %ymm0, %ymm0 # sched: [14:2.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_dpps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vdpps $7, %ymm1, %ymm0, %ymm0 # sched: [13:1.33]
|
|
|
|
; SKYLAKE-NEXT: vdpps $7, (%rdi), %ymm0, %ymm0 # sched: [13:1.33]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_dpps:
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2: # BB#0:
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: vdpps $7, %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; BTVER2-NEXT: vdpps $7, (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_dpps:
|
|
|
|
; ZNVER1: # BB#0:
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vdpps $7, %ymm1, %ymm0, %ymm0 # sched: [100:?]
|
|
|
|
; ZNVER1-NEXT: vdpps $7, (%rdi), %ymm0, %ymm0 # sched: [100:?]
|
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call <8 x float> @llvm.x86.avx.dp.ps.256(<8 x float> %a0, <8 x float> %a1, i8 7)
|
|
|
|
%2 = load <8 x float>, <8 x float> *%a2, align 32
|
|
|
|
%3 = call <8 x float> @llvm.x86.avx.dp.ps.256(<8 x float> %1, <8 x float> %2, i8 7)
|
|
|
|
ret <8 x float> %3
|
2017-04-24 06:08:17 +08:00
|
|
|
}
|
2017-04-24 22:26:30 +08:00
|
|
|
declare <8 x float> @llvm.x86.avx.dp.ps.256(<8 x float>, <8 x float>, i8) nounwind readnone
|
2017-04-24 06:08:17 +08:00
|
|
|
|
2017-04-24 22:26:30 +08:00
|
|
|
define <4 x float> @test_extractf128(<8 x float> %a0, <8 x float> %a1, <4 x float> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_extractf128:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vextractf128 $1, %ymm0, %xmm0 # sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: vextractf128 $1, %ymm1, (%rdi) # sched: [5:1.00]
|
|
|
|
; GENERIC-NEXT: vzeroupper
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_extractf128:
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY: # BB#0:
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vextractf128 $1, %ymm0, %xmm0 # sched: [1:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vextractf128 $1, %ymm1, (%rdi) # sched: [5:1.00]
|
2017-07-27 02:55:14 +08:00
|
|
|
; SANDY-NEXT: vzeroupper
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-LABEL: test_extractf128:
|
2017-04-24 06:08:17 +08:00
|
|
|
; HASWELL: # BB#0:
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vextractf128 $1, %ymm0, %xmm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vextractf128 $1, %ymm1, (%rdi) # sched: [1:1.00]
|
|
|
|
; HASWELL-NEXT: vzeroupper # sched: [4:1.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_extractf128:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vextractf128 $1, %ymm0, %xmm0 # sched: [3:1.00]
|
|
|
|
; SKYLAKE-NEXT: vextractf128 $1, %ymm1, (%rdi) # sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: vzeroupper # sched: [4:1.00]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_extractf128:
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2: # BB#0:
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: vextractf128 $1, %ymm0, %xmm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vextractf128 $1, %ymm1, (%rdi) # sched: [1:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_extractf128:
|
|
|
|
; ZNVER1: # BB#0:
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vextractf128 $1, %ymm0, %xmm0 # sched: [1:0.33]
|
|
|
|
; ZNVER1-NEXT: vextractf128 $1, %ymm1, (%rdi) # sched: [8:0.50]
|
|
|
|
; ZNVER1-NEXT: vzeroupper # sched: [100:?]
|
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = shufflevector <8 x float> %a0, <8 x float> undef, <4 x i32> <i32 4, i32 5, i32 6, i32 7>
|
|
|
|
%2 = shufflevector <8 x float> %a1, <8 x float> undef, <4 x i32> <i32 4, i32 5, i32 6, i32 7>
|
|
|
|
store <4 x float> %2, <4 x float> *%a2
|
|
|
|
ret <4 x float> %1
|
|
|
|
}
|
|
|
|
|
|
|
|
define <4 x double> @test_haddpd(<4 x double> %a0, <4 x double> %a1, <4 x double> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_haddpd:
|
|
|
|
; GENERIC: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vhaddpd %ymm1, %ymm0, %ymm0 # sched: [5:2.00]
|
|
|
|
; GENERIC-NEXT: vhaddpd (%rdi), %ymm0, %ymm0 # sched: [12:2.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_haddpd:
|
|
|
|
; SANDY: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vhaddpd %ymm1, %ymm0, %ymm0 # sched: [5:2.00]
|
|
|
|
; SANDY-NEXT: vhaddpd (%rdi), %ymm0, %ymm0 # sched: [12:2.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_haddpd:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vhaddpd %ymm1, %ymm0, %ymm0 # sched: [5:2.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vhaddpd (%rdi), %ymm0, %ymm0 # sched: [5:2.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_haddpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vhaddpd %ymm1, %ymm0, %ymm0 # sched: [6:2.00]
|
|
|
|
; SKYLAKE-NEXT: vhaddpd (%rdi), %ymm0, %ymm0 # sched: [6:2.00]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_haddpd:
|
|
|
|
; BTVER2: # BB#0:
|
2017-06-09 00:44:13 +08:00
|
|
|
; BTVER2-NEXT: vhaddpd %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
|
|
|
; BTVER2-NEXT: vhaddpd (%rdi), %ymm0, %ymm0 # sched: [8:2.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_haddpd:
|
|
|
|
; ZNVER1: # BB#0:
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vhaddpd %ymm1, %ymm0, %ymm0 # sched: [100:?]
|
|
|
|
; ZNVER1-NEXT: vhaddpd (%rdi), %ymm0, %ymm0 # sched: [100:?]
|
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call <4 x double> @llvm.x86.avx.hadd.pd.256(<4 x double> %a0, <4 x double> %a1)
|
|
|
|
%2 = load <4 x double>, <4 x double> *%a2, align 32
|
|
|
|
%3 = call <4 x double> @llvm.x86.avx.hadd.pd.256(<4 x double> %1, <4 x double> %2)
|
|
|
|
ret <4 x double> %3
|
|
|
|
}
|
|
|
|
declare <4 x double> @llvm.x86.avx.hadd.pd.256(<4 x double>, <4 x double>) nounwind readnone
|
|
|
|
|
|
|
|
define <8 x float> @test_haddps(<8 x float> %a0, <8 x float> %a1, <8 x float> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_haddps:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vhaddps %ymm1, %ymm0, %ymm0 # sched: [5:2.00]
|
|
|
|
; GENERIC-NEXT: vhaddps (%rdi), %ymm0, %ymm0 # sched: [12:2.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_haddps:
|
|
|
|
; SANDY: # BB#0:
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vhaddps %ymm1, %ymm0, %ymm0 # sched: [5:2.00]
|
|
|
|
; SANDY-NEXT: vhaddps (%rdi), %ymm0, %ymm0 # sched: [12:2.00]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_haddps:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vhaddps %ymm1, %ymm0, %ymm0 # sched: [5:2.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vhaddps (%rdi), %ymm0, %ymm0 # sched: [5:2.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_haddps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vhaddps %ymm1, %ymm0, %ymm0 # sched: [6:2.00]
|
|
|
|
; SKYLAKE-NEXT: vhaddps (%rdi), %ymm0, %ymm0 # sched: [6:2.00]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_haddps:
|
|
|
|
; BTVER2: # BB#0:
|
2017-06-09 00:44:13 +08:00
|
|
|
; BTVER2-NEXT: vhaddps %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
|
|
|
; BTVER2-NEXT: vhaddps (%rdi), %ymm0, %ymm0 # sched: [8:2.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_haddps:
|
|
|
|
; ZNVER1: # BB#0:
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vhaddps %ymm1, %ymm0, %ymm0 # sched: [100:?]
|
|
|
|
; ZNVER1-NEXT: vhaddps (%rdi), %ymm0, %ymm0 # sched: [100:?]
|
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call <8 x float> @llvm.x86.avx.hadd.ps.256(<8 x float> %a0, <8 x float> %a1)
|
|
|
|
%2 = load <8 x float>, <8 x float> *%a2, align 32
|
|
|
|
%3 = call <8 x float> @llvm.x86.avx.hadd.ps.256(<8 x float> %1, <8 x float> %2)
|
|
|
|
ret <8 x float> %3
|
|
|
|
}
|
|
|
|
declare <8 x float> @llvm.x86.avx.hadd.ps.256(<8 x float>, <8 x float>) nounwind readnone
|
|
|
|
|
|
|
|
define <4 x double> @test_hsubpd(<4 x double> %a0, <4 x double> %a1, <4 x double> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_hsubpd:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vhsubpd %ymm1, %ymm0, %ymm0 # sched: [5:2.00]
|
|
|
|
; GENERIC-NEXT: vhsubpd (%rdi), %ymm0, %ymm0 # sched: [12:2.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_hsubpd:
|
|
|
|
; SANDY: # BB#0:
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vhsubpd %ymm1, %ymm0, %ymm0 # sched: [5:2.00]
|
|
|
|
; SANDY-NEXT: vhsubpd (%rdi), %ymm0, %ymm0 # sched: [12:2.00]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_hsubpd:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vhsubpd %ymm1, %ymm0, %ymm0 # sched: [5:2.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vhsubpd (%rdi), %ymm0, %ymm0 # sched: [5:2.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_hsubpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vhsubpd %ymm1, %ymm0, %ymm0 # sched: [6:2.00]
|
|
|
|
; SKYLAKE-NEXT: vhsubpd (%rdi), %ymm0, %ymm0 # sched: [6:2.00]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_hsubpd:
|
|
|
|
; BTVER2: # BB#0:
|
2017-06-09 00:44:13 +08:00
|
|
|
; BTVER2-NEXT: vhsubpd %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
|
|
|
; BTVER2-NEXT: vhsubpd (%rdi), %ymm0, %ymm0 # sched: [8:2.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_hsubpd:
|
|
|
|
; ZNVER1: # BB#0:
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vhsubpd %ymm1, %ymm0, %ymm0 # sched: [100:?]
|
|
|
|
; ZNVER1-NEXT: vhsubpd (%rdi), %ymm0, %ymm0 # sched: [100:?]
|
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call <4 x double> @llvm.x86.avx.hsub.pd.256(<4 x double> %a0, <4 x double> %a1)
|
|
|
|
%2 = load <4 x double>, <4 x double> *%a2, align 32
|
|
|
|
%3 = call <4 x double> @llvm.x86.avx.hsub.pd.256(<4 x double> %1, <4 x double> %2)
|
|
|
|
ret <4 x double> %3
|
|
|
|
}
|
|
|
|
declare <4 x double> @llvm.x86.avx.hsub.pd.256(<4 x double>, <4 x double>) nounwind readnone
|
|
|
|
|
|
|
|
define <8 x float> @test_hsubps(<8 x float> %a0, <8 x float> %a1, <8 x float> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_hsubps:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vhsubps %ymm1, %ymm0, %ymm0 # sched: [5:2.00]
|
|
|
|
; GENERIC-NEXT: vhsubps (%rdi), %ymm0, %ymm0 # sched: [12:2.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_hsubps:
|
|
|
|
; SANDY: # BB#0:
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vhsubps %ymm1, %ymm0, %ymm0 # sched: [5:2.00]
|
|
|
|
; SANDY-NEXT: vhsubps (%rdi), %ymm0, %ymm0 # sched: [12:2.00]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_hsubps:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vhsubps %ymm1, %ymm0, %ymm0 # sched: [5:2.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vhsubps (%rdi), %ymm0, %ymm0 # sched: [5:2.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_hsubps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vhsubps %ymm1, %ymm0, %ymm0 # sched: [6:2.00]
|
|
|
|
; SKYLAKE-NEXT: vhsubps (%rdi), %ymm0, %ymm0 # sched: [6:2.00]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_hsubps:
|
|
|
|
; BTVER2: # BB#0:
|
2017-06-09 00:44:13 +08:00
|
|
|
; BTVER2-NEXT: vhsubps %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
|
|
|
; BTVER2-NEXT: vhsubps (%rdi), %ymm0, %ymm0 # sched: [8:2.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_hsubps:
|
|
|
|
; ZNVER1: # BB#0:
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vhsubps %ymm1, %ymm0, %ymm0 # sched: [100:?]
|
|
|
|
; ZNVER1-NEXT: vhsubps (%rdi), %ymm0, %ymm0 # sched: [100:?]
|
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call <8 x float> @llvm.x86.avx.hsub.ps.256(<8 x float> %a0, <8 x float> %a1)
|
|
|
|
%2 = load <8 x float>, <8 x float> *%a2, align 32
|
|
|
|
%3 = call <8 x float> @llvm.x86.avx.hsub.ps.256(<8 x float> %1, <8 x float> %2)
|
|
|
|
ret <8 x float> %3
|
|
|
|
}
|
|
|
|
declare <8 x float> @llvm.x86.avx.hsub.ps.256(<8 x float>, <8 x float>) nounwind readnone
|
|
|
|
|
|
|
|
define <8 x float> @test_insertf128(<8 x float> %a0, <4 x float> %a1, <4 x float> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_insertf128:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vinsertf128 $1, %xmm1, %ymm0, %ymm1 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vinsertf128 $1, (%rdi), %ymm0, %ymm0 # sched: [7:0.50]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_insertf128:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vinsertf128 $1, %xmm1, %ymm0, %ymm1 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vinsertf128 $1, (%rdi), %ymm0, %ymm0 # sched: [7:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_insertf128:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vinsertf128 $1, %xmm1, %ymm0, %ymm1 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vinsertf128 $1, (%rdi), %ymm0, %ymm0 # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_insertf128:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vinsertf128 $1, %xmm1, %ymm0, %ymm1 # sched: [3:1.00]
|
|
|
|
; SKYLAKE-NEXT: vinsertf128 $1, (%rdi), %ymm0, %ymm0 # sched: [1:0.50]
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_insertf128:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vinsertf128 $1, %xmm1, %ymm0, %ymm1 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vinsertf128 $1, (%rdi), %ymm0, %ymm0 # sched: [6:1.00]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [3:2.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_insertf128:
|
|
|
|
; ZNVER1: # BB#0:
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vinsertf128 $1, %xmm1, %ymm0, %ymm1 # sched: [2:0.67]
|
|
|
|
; ZNVER1-NEXT: vinsertf128 $1, (%rdi), %ymm0, %ymm0 # sched: [9:0.67]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = shufflevector <4 x float> %a1, <4 x float> undef, <8 x i32> <i32 0, i32 1, i32 2, i32 3, i32 undef, i32 undef, i32 undef, i32 undef>
|
|
|
|
%2 = shufflevector <8 x float> %a0, <8 x float> %1, <8 x i32> <i32 0, i32 1, i32 2, i32 3, i32 8, i32 9, i32 10, i32 11>
|
|
|
|
%3 = load <4 x float>, <4 x float> *%a2, align 16
|
|
|
|
%4 = shufflevector <4 x float> %3, <4 x float> undef, <8 x i32> <i32 0, i32 1, i32 2, i32 3, i32 undef, i32 undef, i32 undef, i32 undef>
|
|
|
|
%5 = shufflevector <8 x float> %a0, <8 x float> %4, <8 x i32> <i32 0, i32 1, i32 2, i32 3, i32 8, i32 9, i32 10, i32 11>
|
|
|
|
%6 = fadd <8 x float> %2, %5
|
|
|
|
ret <8 x float> %6
|
|
|
|
}
|
|
|
|
|
|
|
|
define <32 x i8> @test_lddqu(i8* %a0) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_lddqu:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vlddqu (%rdi), %ymm0 # sched: [6:0.50]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_lddqu:
|
|
|
|
; SANDY: # BB#0:
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vlddqu (%rdi), %ymm0 # sched: [6:0.50]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_lddqu:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vlddqu (%rdi), %ymm0 # sched: [1:0.50]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_lddqu:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vlddqu (%rdi), %ymm0 # sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_lddqu:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vlddqu (%rdi), %ymm0 # sched: [5:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_lddqu:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vlddqu (%rdi), %ymm0 # sched: [8:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call <32 x i8> @llvm.x86.avx.ldu.dq.256(i8* %a0)
|
|
|
|
ret <32 x i8> %1
|
|
|
|
}
|
|
|
|
declare <32 x i8> @llvm.x86.avx.ldu.dq.256(i8*) nounwind readonly
|
|
|
|
|
|
|
|
define <2 x double> @test_maskmovpd(i8* %a0, <2 x i64> %a1, <2 x double> %a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_maskmovpd:
|
|
|
|
; GENERIC: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vmaskmovpd (%rdi), %xmm0, %xmm2 # sched: [8:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vmaskmovpd %xmm1, %xmm0, (%rdi) # sched: [5:1.00]
|
|
|
|
; GENERIC-NEXT: vmovapd %xmm2, %xmm0 # sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_maskmovpd:
|
|
|
|
; SANDY: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vmaskmovpd (%rdi), %xmm0, %xmm2 # sched: [8:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vmaskmovpd %xmm1, %xmm0, (%rdi) # sched: [5:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vmovapd %xmm2, %xmm0 # sched: [1:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_maskmovpd:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vmaskmovpd (%rdi), %xmm0, %xmm2 # sched: [2:2.00]
|
|
|
|
; HASWELL-NEXT: vmaskmovpd %xmm1, %xmm0, (%rdi) # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vmovapd %xmm2, %xmm0 # sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_maskmovpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vmaskmovpd (%rdi), %xmm0, %xmm2 # sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: vmaskmovpd %xmm1, %xmm0, (%rdi) # sched: [1:1.00]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: vmovapd %xmm2, %xmm0 # sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_maskmovpd:
|
|
|
|
; BTVER2: # BB#0:
|
2017-07-27 02:55:14 +08:00
|
|
|
; BTVER2-NEXT: vmaskmovpd (%rdi), %xmm0, %xmm2
|
|
|
|
; BTVER2-NEXT: vmaskmovpd %xmm1, %xmm0, (%rdi)
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: vmovapd %xmm2, %xmm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_maskmovpd:
|
|
|
|
; ZNVER1: # BB#0:
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vmaskmovpd (%rdi), %xmm0, %xmm2 # sched: [8:0.50]
|
|
|
|
; ZNVER1-NEXT: vmaskmovpd %xmm1, %xmm0, (%rdi) # sched: [4:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; ZNVER1-NEXT: vmovapd %xmm2, %xmm0 # sched: [1:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call <2 x double> @llvm.x86.avx.maskload.pd(i8* %a0, <2 x i64> %a1)
|
|
|
|
call void @llvm.x86.avx.maskstore.pd(i8* %a0, <2 x i64> %a1, <2 x double> %a2)
|
|
|
|
ret <2 x double> %1
|
|
|
|
}
|
|
|
|
declare <2 x double> @llvm.x86.avx.maskload.pd(i8*, <2 x i64>) nounwind readonly
|
|
|
|
declare void @llvm.x86.avx.maskstore.pd(i8*, <2 x i64>, <2 x double>) nounwind
|
|
|
|
|
|
|
|
define <4 x double> @test_maskmovpd_ymm(i8* %a0, <4 x i64> %a1, <4 x double> %a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_maskmovpd_ymm:
|
|
|
|
; GENERIC: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vmaskmovpd (%rdi), %ymm0, %ymm2 # sched: [9:1.00]
|
|
|
|
; GENERIC-NEXT: vmaskmovpd %ymm1, %ymm0, (%rdi) # sched: [5:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vmovapd %ymm2, %ymm0 # sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_maskmovpd_ymm:
|
|
|
|
; SANDY: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vmaskmovpd (%rdi), %ymm0, %ymm2 # sched: [9:1.00]
|
|
|
|
; SANDY-NEXT: vmaskmovpd %ymm1, %ymm0, (%rdi) # sched: [5:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vmovapd %ymm2, %ymm0 # sched: [1:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_maskmovpd_ymm:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vmaskmovpd (%rdi), %ymm0, %ymm2 # sched: [2:2.00]
|
|
|
|
; HASWELL-NEXT: vmaskmovpd %ymm1, %ymm0, (%rdi) # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vmovapd %ymm2, %ymm0 # sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_maskmovpd_ymm:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vmaskmovpd (%rdi), %ymm0, %ymm2 # sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: vmaskmovpd %ymm1, %ymm0, (%rdi) # sched: [1:1.00]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: vmovapd %ymm2, %ymm0 # sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_maskmovpd_ymm:
|
|
|
|
; BTVER2: # BB#0:
|
2017-07-27 02:55:14 +08:00
|
|
|
; BTVER2-NEXT: vmaskmovpd (%rdi), %ymm0, %ymm2
|
|
|
|
; BTVER2-NEXT: vmaskmovpd %ymm1, %ymm0, (%rdi)
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: vmovapd %ymm2, %ymm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_maskmovpd_ymm:
|
|
|
|
; ZNVER1: # BB#0:
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vmaskmovpd (%rdi), %ymm0, %ymm2 # sched: [8:1.00]
|
|
|
|
; ZNVER1-NEXT: vmaskmovpd %ymm1, %ymm0, (%rdi) # sched: [5:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; ZNVER1-NEXT: vmovapd %ymm2, %ymm0 # sched: [1:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call <4 x double> @llvm.x86.avx.maskload.pd.256(i8* %a0, <4 x i64> %a1)
|
|
|
|
call void @llvm.x86.avx.maskstore.pd.256(i8* %a0, <4 x i64> %a1, <4 x double> %a2)
|
|
|
|
ret <4 x double> %1
|
|
|
|
}
|
|
|
|
declare <4 x double> @llvm.x86.avx.maskload.pd.256(i8*, <4 x i64>) nounwind readonly
|
|
|
|
declare void @llvm.x86.avx.maskstore.pd.256(i8*, <4 x i64>, <4 x double>) nounwind
|
|
|
|
|
|
|
|
define <4 x float> @test_maskmovps(i8* %a0, <4 x i32> %a1, <4 x float> %a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_maskmovps:
|
|
|
|
; GENERIC: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vmaskmovps (%rdi), %xmm0, %xmm2 # sched: [8:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vmaskmovps %xmm1, %xmm0, (%rdi) # sched: [5:1.00]
|
|
|
|
; GENERIC-NEXT: vmovaps %xmm2, %xmm0 # sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_maskmovps:
|
|
|
|
; SANDY: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vmaskmovps (%rdi), %xmm0, %xmm2 # sched: [8:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vmaskmovps %xmm1, %xmm0, (%rdi) # sched: [5:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vmovaps %xmm2, %xmm0 # sched: [1:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_maskmovps:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vmaskmovps (%rdi), %xmm0, %xmm2 # sched: [2:2.00]
|
|
|
|
; HASWELL-NEXT: vmaskmovps %xmm1, %xmm0, (%rdi) # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vmovaps %xmm2, %xmm0 # sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_maskmovps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vmaskmovps (%rdi), %xmm0, %xmm2 # sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: vmaskmovps %xmm1, %xmm0, (%rdi) # sched: [1:1.00]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: vmovaps %xmm2, %xmm0 # sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_maskmovps:
|
|
|
|
; BTVER2: # BB#0:
|
2017-07-27 02:55:14 +08:00
|
|
|
; BTVER2-NEXT: vmaskmovps (%rdi), %xmm0, %xmm2
|
|
|
|
; BTVER2-NEXT: vmaskmovps %xmm1, %xmm0, (%rdi)
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: vmovaps %xmm2, %xmm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_maskmovps:
|
|
|
|
; ZNVER1: # BB#0:
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vmaskmovps (%rdi), %xmm0, %xmm2 # sched: [8:0.50]
|
|
|
|
; ZNVER1-NEXT: vmaskmovps %xmm1, %xmm0, (%rdi) # sched: [4:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; ZNVER1-NEXT: vmovaps %xmm2, %xmm0 # sched: [1:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call <4 x float> @llvm.x86.avx.maskload.ps(i8* %a0, <4 x i32> %a1)
|
|
|
|
call void @llvm.x86.avx.maskstore.ps(i8* %a0, <4 x i32> %a1, <4 x float> %a2)
|
|
|
|
ret <4 x float> %1
|
|
|
|
}
|
|
|
|
declare <4 x float> @llvm.x86.avx.maskload.ps(i8*, <4 x i32>) nounwind readonly
|
|
|
|
declare void @llvm.x86.avx.maskstore.ps(i8*, <4 x i32>, <4 x float>) nounwind
|
|
|
|
|
|
|
|
define <8 x float> @test_maskmovps_ymm(i8* %a0, <8 x i32> %a1, <8 x float> %a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_maskmovps_ymm:
|
|
|
|
; GENERIC: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vmaskmovps (%rdi), %ymm0, %ymm2 # sched: [9:1.00]
|
|
|
|
; GENERIC-NEXT: vmaskmovps %ymm1, %ymm0, (%rdi) # sched: [5:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vmovaps %ymm2, %ymm0 # sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_maskmovps_ymm:
|
|
|
|
; SANDY: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vmaskmovps (%rdi), %ymm0, %ymm2 # sched: [9:1.00]
|
|
|
|
; SANDY-NEXT: vmaskmovps %ymm1, %ymm0, (%rdi) # sched: [5:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vmovaps %ymm2, %ymm0 # sched: [1:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_maskmovps_ymm:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vmaskmovps (%rdi), %ymm0, %ymm2 # sched: [2:2.00]
|
|
|
|
; HASWELL-NEXT: vmaskmovps %ymm1, %ymm0, (%rdi) # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vmovaps %ymm2, %ymm0 # sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_maskmovps_ymm:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vmaskmovps (%rdi), %ymm0, %ymm2 # sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: vmaskmovps %ymm1, %ymm0, (%rdi) # sched: [1:1.00]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: vmovaps %ymm2, %ymm0 # sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_maskmovps_ymm:
|
|
|
|
; BTVER2: # BB#0:
|
2017-07-27 02:55:14 +08:00
|
|
|
; BTVER2-NEXT: vmaskmovps (%rdi), %ymm0, %ymm2
|
|
|
|
; BTVER2-NEXT: vmaskmovps %ymm1, %ymm0, (%rdi)
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: vmovaps %ymm2, %ymm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_maskmovps_ymm:
|
|
|
|
; ZNVER1: # BB#0:
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vmaskmovps (%rdi), %ymm0, %ymm2 # sched: [8:1.00]
|
|
|
|
; ZNVER1-NEXT: vmaskmovps %ymm1, %ymm0, (%rdi) # sched: [5:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; ZNVER1-NEXT: vmovaps %ymm2, %ymm0 # sched: [1:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call <8 x float> @llvm.x86.avx.maskload.ps.256(i8* %a0, <8 x i32> %a1)
|
|
|
|
call void @llvm.x86.avx.maskstore.ps.256(i8* %a0, <8 x i32> %a1, <8 x float> %a2)
|
|
|
|
ret <8 x float> %1
|
|
|
|
}
|
|
|
|
declare <8 x float> @llvm.x86.avx.maskload.ps.256(i8*, <8 x i32>) nounwind readonly
|
|
|
|
declare void @llvm.x86.avx.maskstore.ps.256(i8*, <8 x i32>, <8 x float>) nounwind
|
|
|
|
|
|
|
|
define <4 x double> @test_maxpd(<4 x double> %a0, <4 x double> %a1, <4 x double> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_maxpd:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vmaxpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: vmaxpd (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_maxpd:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vmaxpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vmaxpd (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_maxpd:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vmaxpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vmaxpd (%rdi), %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_maxpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vmaxpd %ymm1, %ymm0, %ymm0 # sched: [4:0.33]
|
|
|
|
; SKYLAKE-NEXT: vmaxpd (%rdi), %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_maxpd:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vmaxpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; BTVER2-NEXT: vmaxpd (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_maxpd:
|
|
|
|
; ZNVER1: # BB#0:
|
|
|
|
; ZNVER1-NEXT: vmaxpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vmaxpd (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call <4 x double> @llvm.x86.avx.max.pd.256(<4 x double> %a0, <4 x double> %a1)
|
|
|
|
%2 = load <4 x double>, <4 x double> *%a2, align 32
|
|
|
|
%3 = call <4 x double> @llvm.x86.avx.max.pd.256(<4 x double> %1, <4 x double> %2)
|
|
|
|
ret <4 x double> %3
|
|
|
|
}
|
|
|
|
declare <4 x double> @llvm.x86.avx.max.pd.256(<4 x double>, <4 x double>) nounwind readnone
|
|
|
|
|
|
|
|
define <8 x float> @test_maxps(<8 x float> %a0, <8 x float> %a1, <8 x float> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_maxps:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vmaxps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: vmaxps (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_maxps:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vmaxps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vmaxps (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_maxps:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vmaxps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vmaxps (%rdi), %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_maxps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vmaxps %ymm1, %ymm0, %ymm0 # sched: [4:0.33]
|
|
|
|
; SKYLAKE-NEXT: vmaxps (%rdi), %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_maxps:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vmaxps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; BTVER2-NEXT: vmaxps (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_maxps:
|
|
|
|
; ZNVER1: # BB#0:
|
|
|
|
; ZNVER1-NEXT: vmaxps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vmaxps (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call <8 x float> @llvm.x86.avx.max.ps.256(<8 x float> %a0, <8 x float> %a1)
|
|
|
|
%2 = load <8 x float>, <8 x float> *%a2, align 32
|
|
|
|
%3 = call <8 x float> @llvm.x86.avx.max.ps.256(<8 x float> %1, <8 x float> %2)
|
|
|
|
ret <8 x float> %3
|
|
|
|
}
|
|
|
|
declare <8 x float> @llvm.x86.avx.max.ps.256(<8 x float>, <8 x float>) nounwind readnone
|
|
|
|
|
|
|
|
define <4 x double> @test_minpd(<4 x double> %a0, <4 x double> %a1, <4 x double> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_minpd:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vminpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vminpd (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_minpd:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vminpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vminpd (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_minpd:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vminpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vminpd (%rdi), %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_minpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vminpd %ymm1, %ymm0, %ymm0 # sched: [4:0.33]
|
|
|
|
; SKYLAKE-NEXT: vminpd (%rdi), %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_minpd:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vminpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; BTVER2-NEXT: vminpd (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_minpd:
|
|
|
|
; ZNVER1: # BB#0:
|
|
|
|
; ZNVER1-NEXT: vminpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vminpd (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call <4 x double> @llvm.x86.avx.min.pd.256(<4 x double> %a0, <4 x double> %a1)
|
|
|
|
%2 = load <4 x double>, <4 x double> *%a2, align 32
|
|
|
|
%3 = call <4 x double> @llvm.x86.avx.min.pd.256(<4 x double> %1, <4 x double> %2)
|
|
|
|
ret <4 x double> %3
|
|
|
|
}
|
|
|
|
declare <4 x double> @llvm.x86.avx.min.pd.256(<4 x double>, <4 x double>) nounwind readnone
|
|
|
|
|
|
|
|
define <8 x float> @test_minps(<8 x float> %a0, <8 x float> %a1, <8 x float> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_minps:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vminps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vminps (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_minps:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vminps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vminps (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_minps:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vminps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vminps (%rdi), %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_minps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vminps %ymm1, %ymm0, %ymm0 # sched: [4:0.33]
|
|
|
|
; SKYLAKE-NEXT: vminps (%rdi), %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_minps:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vminps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; BTVER2-NEXT: vminps (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_minps:
|
|
|
|
; ZNVER1: # BB#0:
|
|
|
|
; ZNVER1-NEXT: vminps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vminps (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call <8 x float> @llvm.x86.avx.min.ps.256(<8 x float> %a0, <8 x float> %a1)
|
|
|
|
%2 = load <8 x float>, <8 x float> *%a2, align 32
|
|
|
|
%3 = call <8 x float> @llvm.x86.avx.min.ps.256(<8 x float> %1, <8 x float> %2)
|
|
|
|
ret <8 x float> %3
|
|
|
|
}
|
|
|
|
declare <8 x float> @llvm.x86.avx.min.ps.256(<8 x float>, <8 x float>) nounwind readnone
|
|
|
|
|
|
|
|
define <4 x double> @test_movapd(<4 x double> *%a0, <4 x double> *%a1) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_movapd:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vmovapd (%rdi), %ymm0 # sched: [7:0.50]
|
|
|
|
; GENERIC-NEXT: vaddpd %ymm0, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: vmovapd %ymm0, (%rsi) # sched: [5:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_movapd:
|
|
|
|
; SANDY: # BB#0:
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vmovapd (%rdi), %ymm0 # sched: [7:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vaddpd %ymm0, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vmovapd %ymm0, (%rsi) # sched: [5:1.00]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_movapd:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vmovapd (%rdi), %ymm0 # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vaddpd %ymm0, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-06-28 19:23:31 +08:00
|
|
|
; HASWELL-NEXT: vmovapd %ymm0, (%rsi) # sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_movapd:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vmovapd (%rdi), %ymm0 # sched: [1:0.50]
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vaddpd %ymm0, %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: vmovapd %ymm0, (%rsi) # sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_movapd:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vmovapd (%rdi), %ymm0 # sched: [5:1.00]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddpd %ymm0, %ymm0, %ymm0 # sched: [3:2.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: vmovapd %ymm0, (%rsi) # sched: [1:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_movapd:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vmovapd (%rdi), %ymm0 # sched: [8:0.50]
|
|
|
|
; ZNVER1-NEXT: vaddpd %ymm0, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; ZNVER1-NEXT: vmovapd %ymm0, (%rsi) # sched: [1:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = load <4 x double>, <4 x double> *%a0, align 32
|
|
|
|
%2 = fadd <4 x double> %1, %1
|
|
|
|
store <4 x double> %2, <4 x double> *%a1, align 32
|
|
|
|
ret <4 x double> %2
|
|
|
|
}
|
|
|
|
|
|
|
|
define <8 x float> @test_movaps(<8 x float> *%a0, <8 x float> *%a1) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_movaps:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vmovaps (%rdi), %ymm0 # sched: [7:0.50]
|
|
|
|
; GENERIC-NEXT: vaddps %ymm0, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: vmovaps %ymm0, (%rsi) # sched: [5:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_movaps:
|
|
|
|
; SANDY: # BB#0:
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vmovaps (%rdi), %ymm0 # sched: [7:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vaddps %ymm0, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vmovaps %ymm0, (%rsi) # sched: [5:1.00]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_movaps:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vmovaps (%rdi), %ymm0 # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vaddps %ymm0, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-06-28 19:23:31 +08:00
|
|
|
; HASWELL-NEXT: vmovaps %ymm0, (%rsi) # sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_movaps:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vmovaps (%rdi), %ymm0 # sched: [1:0.50]
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vaddps %ymm0, %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: vmovaps %ymm0, (%rsi) # sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_movaps:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vmovaps (%rdi), %ymm0 # sched: [5:1.00]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddps %ymm0, %ymm0, %ymm0 # sched: [3:2.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: vmovaps %ymm0, (%rsi) # sched: [1:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_movaps:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vmovaps (%rdi), %ymm0 # sched: [8:0.50]
|
|
|
|
; ZNVER1-NEXT: vaddps %ymm0, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; ZNVER1-NEXT: vmovaps %ymm0, (%rsi) # sched: [1:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = load <8 x float>, <8 x float> *%a0, align 32
|
|
|
|
%2 = fadd <8 x float> %1, %1
|
|
|
|
store <8 x float> %2, <8 x float> *%a1, align 32
|
|
|
|
ret <8 x float> %2
|
|
|
|
}
|
|
|
|
|
|
|
|
define <4 x double> @test_movddup(<4 x double> %a0, <4 x double> *%a1) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_movddup:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vmovddup {{.*#+}} ymm0 = ymm0[0,0,2,2] sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: vmovddup {{.*#+}} ymm1 = mem[0,0,2,2] sched: [7:0.50]
|
|
|
|
; GENERIC-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_movddup:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vmovddup {{.*#+}} ymm0 = ymm0[0,0,2,2] sched: [1:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vmovddup {{.*#+}} ymm1 = mem[0,0,2,2] sched: [7:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_movddup:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vmovddup {{.*#+}} ymm0 = ymm0[0,0,2,2] sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vmovddup {{.*#+}} ymm1 = mem[0,0,2,2] sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_movddup:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vmovddup {{.*#+}} ymm0 = ymm0[0,0,2,2] sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: vmovddup {{.*#+}} ymm1 = mem[0,0,2,2] sched: [1:0.50]
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_movddup:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vmovddup {{.*#+}} ymm1 = mem[0,0,2,2] sched: [5:1.00]
|
|
|
|
; BTVER2-NEXT: vmovddup {{.*#+}} ymm0 = ymm0[0,0,2,2] sched: [1:0.50]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_movddup:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vmovddup {{.*#+}} ymm1 = mem[0,0,2,2] sched: [8:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; ZNVER1-NEXT: vmovddup {{.*#+}} ymm0 = ymm0[0,0,2,2] sched: [1:0.50]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = shufflevector <4 x double> %a0, <4 x double> undef, <4 x i32> <i32 0, i32 0, i32 2, i32 2>
|
|
|
|
%2 = load <4 x double>, <4 x double> *%a1, align 32
|
|
|
|
%3 = shufflevector <4 x double> %2, <4 x double> undef, <4 x i32> <i32 0, i32 0, i32 2, i32 2>
|
|
|
|
%4 = fadd <4 x double> %1, %3
|
|
|
|
ret <4 x double> %4
|
|
|
|
}
|
|
|
|
|
|
|
|
define i32 @test_movmskpd(<4 x double> %a0) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_movmskpd:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vmovmskpd %ymm0, %eax # sched: [2:1.00]
|
|
|
|
; GENERIC-NEXT: vzeroupper
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_movmskpd:
|
|
|
|
; SANDY: # BB#0:
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vmovmskpd %ymm0, %eax # sched: [2:1.00]
|
2017-07-27 02:55:14 +08:00
|
|
|
; SANDY-NEXT: vzeroupper
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_movmskpd:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vmovmskpd %ymm0, %eax # sched: [3:1.00]
|
|
|
|
; HASWELL-NEXT: vzeroupper # sched: [4:1.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_movmskpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vmovmskpd %ymm0, %eax # sched: [2:1.00]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: vzeroupper # sched: [4:1.00]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_movmskpd:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vmovmskpd %ymm0, %eax # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_movmskpd:
|
|
|
|
; ZNVER1: # BB#0:
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vmovmskpd %ymm0, %eax # sched: [1:1.00]
|
|
|
|
; ZNVER1-NEXT: vzeroupper # sched: [100:?]
|
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call i32 @llvm.x86.avx.movmsk.pd.256(<4 x double> %a0)
|
|
|
|
ret i32 %1
|
|
|
|
}
|
|
|
|
declare i32 @llvm.x86.avx.movmsk.pd.256(<4 x double>) nounwind readnone
|
|
|
|
|
|
|
|
define i32 @test_movmskps(<8 x float> %a0) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_movmskps:
|
|
|
|
; GENERIC: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vmovmskps %ymm0, %eax # sched: [2:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vzeroupper
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_movmskps:
|
|
|
|
; SANDY: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vmovmskps %ymm0, %eax # sched: [2:1.00]
|
2017-07-27 02:55:14 +08:00
|
|
|
; SANDY-NEXT: vzeroupper
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_movmskps:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vmovmskps %ymm0, %eax # sched: [3:1.00]
|
|
|
|
; HASWELL-NEXT: vzeroupper # sched: [4:1.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_movmskps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vmovmskps %ymm0, %eax # sched: [2:1.00]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: vzeroupper # sched: [4:1.00]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_movmskps:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vmovmskps %ymm0, %eax # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_movmskps:
|
|
|
|
; ZNVER1: # BB#0:
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vmovmskps %ymm0, %eax # sched: [1:1.00]
|
|
|
|
; ZNVER1-NEXT: vzeroupper # sched: [100:?]
|
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call i32 @llvm.x86.avx.movmsk.ps.256(<8 x float> %a0)
|
|
|
|
ret i32 %1
|
|
|
|
}
|
|
|
|
declare i32 @llvm.x86.avx.movmsk.ps.256(<8 x float>) nounwind readnone
|
|
|
|
|
|
|
|
define <4 x double> @test_movntpd(<4 x double> %a0, <4 x double> *%a1) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_movntpd:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vaddpd %ymm0, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: vmovntpd %ymm0, (%rdi) # sched: [5:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_movntpd:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vaddpd %ymm0, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vmovntpd %ymm0, (%rdi) # sched: [5:1.00]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_movntpd:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vaddpd %ymm0, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-06-28 19:23:31 +08:00
|
|
|
; HASWELL-NEXT: vmovntpd %ymm0, (%rdi) # sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_movntpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vaddpd %ymm0, %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: vmovntpd %ymm0, (%rdi) # sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_movntpd:
|
|
|
|
; BTVER2: # BB#0:
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddpd %ymm0, %ymm0, %ymm0 # sched: [3:2.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: vmovntpd %ymm0, (%rdi) # sched: [1:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_movntpd:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vaddpd %ymm0, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; ZNVER1-NEXT: vmovntpd %ymm0, (%rdi) # sched: [1:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = fadd <4 x double> %a0, %a0
|
|
|
|
store <4 x double> %1, <4 x double> *%a1, align 32, !nontemporal !0
|
|
|
|
ret <4 x double> %1
|
|
|
|
}
|
|
|
|
|
|
|
|
define <8 x float> @test_movntps(<8 x float> %a0, <8 x float> *%a1) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_movntps:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vaddps %ymm0, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: vmovntps %ymm0, (%rdi) # sched: [5:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_movntps:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vaddps %ymm0, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vmovntps %ymm0, (%rdi) # sched: [5:1.00]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_movntps:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vaddps %ymm0, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-06-28 19:23:31 +08:00
|
|
|
; HASWELL-NEXT: vmovntps %ymm0, (%rdi) # sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_movntps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vaddps %ymm0, %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: vmovntps %ymm0, (%rdi) # sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_movntps:
|
|
|
|
; BTVER2: # BB#0:
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddps %ymm0, %ymm0, %ymm0 # sched: [3:2.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: vmovntps %ymm0, (%rdi) # sched: [1:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_movntps:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vaddps %ymm0, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; ZNVER1-NEXT: vmovntps %ymm0, (%rdi) # sched: [1:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = fadd <8 x float> %a0, %a0
|
|
|
|
store <8 x float> %1, <8 x float> *%a1, align 32, !nontemporal !0
|
|
|
|
ret <8 x float> %1
|
|
|
|
}
|
|
|
|
|
|
|
|
define <8 x float> @test_movshdup(<8 x float> %a0, <8 x float> *%a1) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_movshdup:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vmovshdup {{.*#+}} ymm0 = ymm0[1,1,3,3,5,5,7,7] sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: vmovshdup {{.*#+}} ymm1 = mem[1,1,3,3,5,5,7,7] sched: [7:0.50]
|
|
|
|
; GENERIC-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_movshdup:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vmovshdup {{.*#+}} ymm0 = ymm0[1,1,3,3,5,5,7,7] sched: [1:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vmovshdup {{.*#+}} ymm1 = mem[1,1,3,3,5,5,7,7] sched: [7:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_movshdup:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vmovshdup {{.*#+}} ymm0 = ymm0[1,1,3,3,5,5,7,7] sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vmovshdup {{.*#+}} ymm1 = mem[1,1,3,3,5,5,7,7] sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_movshdup:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vmovshdup {{.*#+}} ymm0 = ymm0[1,1,3,3,5,5,7,7] sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: vmovshdup {{.*#+}} ymm1 = mem[1,1,3,3,5,5,7,7] sched: [1:0.50]
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_movshdup:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vmovshdup {{.*#+}} ymm1 = mem[1,1,3,3,5,5,7,7] sched: [5:1.00]
|
|
|
|
; BTVER2-NEXT: vmovshdup {{.*#+}} ymm0 = ymm0[1,1,3,3,5,5,7,7] sched: [1:0.50]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_movshdup:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vmovshdup {{.*#+}} ymm1 = mem[1,1,3,3,5,5,7,7] sched: [8:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; ZNVER1-NEXT: vmovshdup {{.*#+}} ymm0 = ymm0[1,1,3,3,5,5,7,7] sched: [1:0.50]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = shufflevector <8 x float> %a0, <8 x float> undef, <8 x i32> <i32 1, i32 1, i32 3, i32 3, i32 5, i32 5, i32 7, i32 7>
|
|
|
|
%2 = load <8 x float>, <8 x float> *%a1, align 32
|
|
|
|
%3 = shufflevector <8 x float> %2, <8 x float> undef, <8 x i32> <i32 1, i32 1, i32 3, i32 3, i32 5, i32 5, i32 7, i32 7>
|
|
|
|
%4 = fadd <8 x float> %1, %3
|
|
|
|
ret <8 x float> %4
|
|
|
|
}
|
|
|
|
|
|
|
|
define <8 x float> @test_movsldup(<8 x float> %a0, <8 x float> *%a1) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_movsldup:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vmovsldup {{.*#+}} ymm0 = ymm0[0,0,2,2,4,4,6,6] sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: vmovsldup {{.*#+}} ymm1 = mem[0,0,2,2,4,4,6,6] sched: [7:0.50]
|
|
|
|
; GENERIC-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_movsldup:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vmovsldup {{.*#+}} ymm0 = ymm0[0,0,2,2,4,4,6,6] sched: [1:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vmovsldup {{.*#+}} ymm1 = mem[0,0,2,2,4,4,6,6] sched: [7:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_movsldup:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vmovsldup {{.*#+}} ymm0 = ymm0[0,0,2,2,4,4,6,6] sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vmovsldup {{.*#+}} ymm1 = mem[0,0,2,2,4,4,6,6] sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_movsldup:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vmovsldup {{.*#+}} ymm0 = ymm0[0,0,2,2,4,4,6,6] sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: vmovsldup {{.*#+}} ymm1 = mem[0,0,2,2,4,4,6,6] sched: [1:0.50]
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_movsldup:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vmovsldup {{.*#+}} ymm1 = mem[0,0,2,2,4,4,6,6] sched: [5:1.00]
|
|
|
|
; BTVER2-NEXT: vmovsldup {{.*#+}} ymm0 = ymm0[0,0,2,2,4,4,6,6] sched: [1:0.50]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_movsldup:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vmovsldup {{.*#+}} ymm1 = mem[0,0,2,2,4,4,6,6] sched: [8:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; ZNVER1-NEXT: vmovsldup {{.*#+}} ymm0 = ymm0[0,0,2,2,4,4,6,6] sched: [1:0.50]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = shufflevector <8 x float> %a0, <8 x float> undef, <8 x i32> <i32 0, i32 0, i32 2, i32 2, i32 4, i32 4, i32 6, i32 6>
|
|
|
|
%2 = load <8 x float>, <8 x float> *%a1, align 32
|
|
|
|
%3 = shufflevector <8 x float> %2, <8 x float> undef, <8 x i32> <i32 0, i32 0, i32 2, i32 2, i32 4, i32 4, i32 6, i32 6>
|
|
|
|
%4 = fadd <8 x float> %1, %3
|
|
|
|
ret <8 x float> %4
|
|
|
|
}
|
|
|
|
|
|
|
|
define <4 x double> @test_movupd(<4 x double> *%a0, <4 x double> *%a1) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_movupd:
|
|
|
|
; GENERIC: # BB#0:
|
2017-08-25 08:56:05 +08:00
|
|
|
; GENERIC-NEXT: vmovupd (%rdi), %ymm0 # sched: [7:0.50]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vaddpd %ymm0, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-25 08:56:05 +08:00
|
|
|
; GENERIC-NEXT: vmovupd %ymm0, (%rsi) # sched: [5:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_movupd:
|
|
|
|
; SANDY: # BB#0:
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vmovups (%rdi), %xmm0 # sched: [6:0.50]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vinsertf128 $1, 16(%rdi), %ymm0, %ymm0 # sched: [7:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vaddpd %ymm0, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vextractf128 $1, %ymm0, 16(%rsi) # sched: [5:1.00]
|
|
|
|
; SANDY-NEXT: vmovupd %xmm0, (%rsi) # sched: [5:1.00]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_movupd:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vmovupd (%rdi), %ymm0 # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vaddpd %ymm0, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-06-28 19:23:31 +08:00
|
|
|
; HASWELL-NEXT: vmovupd %ymm0, (%rsi) # sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_movupd:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vmovupd (%rdi), %ymm0 # sched: [1:0.50]
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vaddpd %ymm0, %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: vmovupd %ymm0, (%rsi) # sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_movupd:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vmovupd (%rdi), %ymm0 # sched: [5:1.00]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddpd %ymm0, %ymm0, %ymm0 # sched: [3:2.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: vmovupd %ymm0, (%rsi) # sched: [1:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_movupd:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vmovupd (%rdi), %ymm0 # sched: [8:0.50]
|
|
|
|
; ZNVER1-NEXT: vaddpd %ymm0, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; ZNVER1-NEXT: vmovupd %ymm0, (%rsi) # sched: [1:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = load <4 x double>, <4 x double> *%a0, align 1
|
|
|
|
%2 = fadd <4 x double> %1, %1
|
|
|
|
store <4 x double> %2, <4 x double> *%a1, align 1
|
|
|
|
ret <4 x double> %2
|
|
|
|
}
|
|
|
|
|
|
|
|
define <8 x float> @test_movups(<8 x float> *%a0, <8 x float> *%a1) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_movups:
|
|
|
|
; GENERIC: # BB#0:
|
2017-08-25 08:56:05 +08:00
|
|
|
; GENERIC-NEXT: vmovups (%rdi), %ymm0 # sched: [7:0.50]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vaddps %ymm0, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-25 08:56:05 +08:00
|
|
|
; GENERIC-NEXT: vmovups %ymm0, (%rsi) # sched: [5:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_movups:
|
|
|
|
; SANDY: # BB#0:
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vmovups (%rdi), %xmm0 # sched: [6:0.50]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vinsertf128 $1, 16(%rdi), %ymm0, %ymm0 # sched: [7:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vaddps %ymm0, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vextractf128 $1, %ymm0, 16(%rsi) # sched: [5:1.00]
|
|
|
|
; SANDY-NEXT: vmovups %xmm0, (%rsi) # sched: [5:1.00]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_movups:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vmovups (%rdi), %ymm0 # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vaddps %ymm0, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-06-28 19:23:31 +08:00
|
|
|
; HASWELL-NEXT: vmovups %ymm0, (%rsi) # sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_movups:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vmovups (%rdi), %ymm0 # sched: [1:0.50]
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vaddps %ymm0, %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: vmovups %ymm0, (%rsi) # sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_movups:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vmovups (%rdi), %ymm0 # sched: [5:1.00]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddps %ymm0, %ymm0, %ymm0 # sched: [3:2.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: vmovups %ymm0, (%rsi) # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_movups:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vmovups (%rdi), %ymm0 # sched: [8:0.50]
|
|
|
|
; ZNVER1-NEXT: vaddps %ymm0, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; ZNVER1-NEXT: vmovups %ymm0, (%rsi) # sched: [1:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = load <8 x float>, <8 x float> *%a0, align 1
|
|
|
|
%2 = fadd <8 x float> %1, %1
|
|
|
|
store <8 x float> %2, <8 x float> *%a1, align 1
|
|
|
|
ret <8 x float> %2
|
2017-04-24 06:08:17 +08:00
|
|
|
}
|
|
|
|
|
|
|
|
define <4 x double> @test_mulpd(<4 x double> %a0, <4 x double> %a1, <4 x double> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_mulpd:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vmulpd %ymm1, %ymm0, %ymm0 # sched: [5:1.00]
|
|
|
|
; GENERIC-NEXT: vmulpd (%rdi), %ymm0, %ymm0 # sched: [12:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-LABEL: test_mulpd:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vmulpd %ymm1, %ymm0, %ymm0 # sched: [5:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vmulpd (%rdi), %ymm0, %ymm0 # sched: [12:1.00]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_mulpd:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vmulpd %ymm1, %ymm0, %ymm0 # sched: [5:0.50]
|
|
|
|
; HASWELL-NEXT: vmulpd (%rdi), %ymm0, %ymm0 # sched: [5:0.50]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_mulpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vmulpd %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
|
|
|
; SKYLAKE-NEXT: vmulpd (%rdi), %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-LABEL: test_mulpd:
|
|
|
|
; BTVER2: # BB#0:
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vmulpd %ymm1, %ymm0, %ymm0 # sched: [4:4.00]
|
|
|
|
; BTVER2-NEXT: vmulpd (%rdi), %ymm0, %ymm0 # sched: [9:4.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_mulpd:
|
|
|
|
; ZNVER1: # BB#0:
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vmulpd %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
|
|
|
; ZNVER1-NEXT: vmulpd (%rdi), %ymm0, %ymm0 # sched: [11:0.50]
|
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 06:08:17 +08:00
|
|
|
%1 = fmul <4 x double> %a0, %a1
|
|
|
|
%2 = load <4 x double>, <4 x double> *%a2, align 32
|
|
|
|
%3 = fmul <4 x double> %1, %2
|
|
|
|
ret <4 x double> %3
|
|
|
|
}
|
|
|
|
|
|
|
|
define <8 x float> @test_mulps(<8 x float> %a0, <8 x float> %a1, <8 x float> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_mulps:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vmulps %ymm1, %ymm0, %ymm0 # sched: [5:1.00]
|
|
|
|
; GENERIC-NEXT: vmulps (%rdi), %ymm0, %ymm0 # sched: [12:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-LABEL: test_mulps:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vmulps %ymm1, %ymm0, %ymm0 # sched: [5:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vmulps (%rdi), %ymm0, %ymm0 # sched: [12:1.00]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_mulps:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vmulps %ymm1, %ymm0, %ymm0 # sched: [5:0.50]
|
|
|
|
; HASWELL-NEXT: vmulps (%rdi), %ymm0, %ymm0 # sched: [5:0.50]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_mulps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vmulps %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
|
|
|
; SKYLAKE-NEXT: vmulps (%rdi), %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-LABEL: test_mulps:
|
|
|
|
; BTVER2: # BB#0:
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vmulps %ymm1, %ymm0, %ymm0 # sched: [2:2.00]
|
|
|
|
; BTVER2-NEXT: vmulps (%rdi), %ymm0, %ymm0 # sched: [7:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_mulps:
|
|
|
|
; ZNVER1: # BB#0:
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vmulps %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
|
|
|
; ZNVER1-NEXT: vmulps (%rdi), %ymm0, %ymm0 # sched: [11:0.50]
|
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 06:08:17 +08:00
|
|
|
%1 = fmul <8 x float> %a0, %a1
|
|
|
|
%2 = load <8 x float>, <8 x float> *%a2, align 32
|
|
|
|
%3 = fmul <8 x float> %1, %2
|
|
|
|
ret <8 x float> %3
|
|
|
|
}
|
|
|
|
|
|
|
|
define <4 x double> @orpd(<4 x double> %a0, <4 x double> %a1, <4 x double> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: orpd:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vorpd %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: vorpd (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
|
|
|
; GENERIC-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-LABEL: orpd:
|
|
|
|
; SANDY: # BB#0:
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vorpd %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
|
|
|
; SANDY-NEXT: vorpd (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: orpd:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vorpd %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vorpd (%rdi), %ymm0, %ymm0 # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; HASWELL-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: orpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vorpd %ymm1, %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: vorpd (%rdi), %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-LABEL: orpd:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vorpd %ymm1, %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vorpd (%rdi), %ymm0, %ymm0 # sched: [6:1.00]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: orpd:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vorpd %ymm1, %ymm0, %ymm0 # sched: [1:0.25]
|
|
|
|
; ZNVER1-NEXT: vorpd (%rdi), %ymm0, %ymm0 # sched: [8:0.50]
|
|
|
|
; ZNVER1-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 06:08:17 +08:00
|
|
|
%1 = bitcast <4 x double> %a0 to <4 x i64>
|
|
|
|
%2 = bitcast <4 x double> %a1 to <4 x i64>
|
|
|
|
%3 = or <4 x i64> %1, %2
|
|
|
|
%4 = load <4 x double>, <4 x double> *%a2, align 32
|
|
|
|
%5 = bitcast <4 x double> %4 to <4 x i64>
|
|
|
|
%6 = or <4 x i64> %3, %5
|
|
|
|
%7 = bitcast <4 x i64> %6 to <4 x double>
|
|
|
|
%8 = fadd <4 x double> %a1, %7
|
|
|
|
ret <4 x double> %8
|
|
|
|
}
|
|
|
|
|
|
|
|
define <8 x float> @test_orps(<8 x float> %a0, <8 x float> %a1, <8 x float> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_orps:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vorps %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: vorps (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
|
|
|
; GENERIC-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-LABEL: test_orps:
|
|
|
|
; SANDY: # BB#0:
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vorps %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
|
|
|
; SANDY-NEXT: vorps (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_orps:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vorps %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vorps (%rdi), %ymm0, %ymm0 # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; HASWELL-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_orps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vorps %ymm1, %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: vorps (%rdi), %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-LABEL: test_orps:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vorps %ymm1, %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vorps (%rdi), %ymm0, %ymm0 # sched: [6:1.00]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [3:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_orps:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vorps %ymm1, %ymm0, %ymm0 # sched: [1:0.25]
|
|
|
|
; ZNVER1-NEXT: vorps (%rdi), %ymm0, %ymm0 # sched: [8:0.50]
|
|
|
|
; ZNVER1-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 06:08:17 +08:00
|
|
|
%1 = bitcast <8 x float> %a0 to <4 x i64>
|
|
|
|
%2 = bitcast <8 x float> %a1 to <4 x i64>
|
|
|
|
%3 = or <4 x i64> %1, %2
|
|
|
|
%4 = load <8 x float>, <8 x float> *%a2, align 32
|
|
|
|
%5 = bitcast <8 x float> %4 to <4 x i64>
|
|
|
|
%6 = or <4 x i64> %3, %5
|
|
|
|
%7 = bitcast <4 x i64> %6 to <8 x float>
|
|
|
|
%8 = fadd <8 x float> %a1, %7
|
|
|
|
ret <8 x float> %8
|
|
|
|
}
|
|
|
|
|
2017-09-12 19:10:59 +08:00
|
|
|
define <4 x double> @test_perm2f128(<4 x double> %a0, <4 x double> %a1, <4 x double> *%a2) {
|
|
|
|
; GENERIC-LABEL: test_perm2f128:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vperm2f128 {{.*#+}} ymm1 = ymm0[2,3],ymm1[0,1] sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: vperm2f128 {{.*#+}} ymm0 = ymm0[2,3],mem[0,1] sched: [8:1.00]
|
|
|
|
; GENERIC-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
|
|
|
; SANDY-LABEL: test_perm2f128:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vperm2f128 {{.*#+}} ymm1 = ymm0[2,3],ymm1[0,1] sched: [1:1.00]
|
|
|
|
; SANDY-NEXT: vperm2f128 {{.*#+}} ymm0 = ymm0[2,3],mem[0,1] sched: [8:1.00]
|
|
|
|
; SANDY-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_perm2f128:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vperm2f128 {{.*#+}} ymm1 = ymm0[2,3],ymm1[0,1] sched: [3:1.00]
|
|
|
|
; HASWELL-NEXT: vperm2f128 {{.*#+}} ymm0 = ymm0[2,3],mem[0,1] sched: [3:1.00]
|
|
|
|
; HASWELL-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
|
|
|
; SKYLAKE-LABEL: test_perm2f128:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vperm2f128 {{.*#+}} ymm1 = ymm0[2,3],ymm1[0,1] sched: [3:1.00]
|
|
|
|
; SKYLAKE-NEXT: vperm2f128 {{.*#+}} ymm0 = ymm0[2,3],mem[0,1] sched: [3:1.00]
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [4:0.50]
|
2017-09-12 19:10:59 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
|
|
|
; BTVER2-LABEL: test_perm2f128:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vperm2f128 {{.*#+}} ymm1 = ymm0[2,3],ymm1[0,1] sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vperm2f128 {{.*#+}} ymm0 = ymm0[2,3],mem[0,1] sched: [6:1.00]
|
|
|
|
; BTVER2-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:2.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_perm2f128:
|
|
|
|
; ZNVER1: # BB#0:
|
|
|
|
; ZNVER1-NEXT: vperm2f128 {{.*#+}} ymm1 = ymm0[2,3],ymm1[0,1] sched: [100:?]
|
|
|
|
; ZNVER1-NEXT: vperm2f128 {{.*#+}} ymm0 = ymm0[2,3],mem[0,1] sched: [100:?]
|
|
|
|
; ZNVER1-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
|
|
|
%1 = shufflevector <4 x double> %a0, <4 x double> %a1, <4 x i32> <i32 2, i32 3, i32 4, i32 5>
|
|
|
|
%2 = load <4 x double>, <4 x double> *%a2, align 32
|
|
|
|
%3 = shufflevector <4 x double> %a0, <4 x double> %2, <4 x i32> <i32 2, i32 3, i32 4, i32 5>
|
|
|
|
%4 = fadd <4 x double> %1, %3
|
|
|
|
ret <4 x double> %4
|
|
|
|
}
|
|
|
|
|
2017-04-24 22:26:30 +08:00
|
|
|
define <2 x double> @test_permilpd(<2 x double> %a0, <2 x double> *%a1) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_permilpd:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vpermilpd {{.*#+}} xmm0 = xmm0[1,0] sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: vpermilpd {{.*#+}} xmm1 = mem[1,0] sched: [7:1.00]
|
|
|
|
; GENERIC-NEXT: vaddpd %xmm1, %xmm0, %xmm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_permilpd:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vpermilpd {{.*#+}} xmm0 = xmm0[1,0] sched: [1:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vpermilpd {{.*#+}} xmm1 = mem[1,0] sched: [7:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vaddpd %xmm1, %xmm0, %xmm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_permilpd:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vpermilpd {{.*#+}} xmm0 = xmm0[1,0] sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vpermilpd {{.*#+}} xmm1 = mem[1,0] sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vaddpd %xmm1, %xmm0, %xmm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_permilpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vpermilpd {{.*#+}} xmm0 = xmm0[1,0] sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: vpermilpd {{.*#+}} xmm1 = mem[1,0] sched: [1:1.00]
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vaddpd %xmm1, %xmm0, %xmm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_permilpd:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vpermilpd {{.*#+}} xmm1 = mem[1,0] sched: [6:1.00]
|
|
|
|
; BTVER2-NEXT: vpermilpd {{.*#+}} xmm0 = xmm0[1,0] sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vaddpd %xmm1, %xmm0, %xmm0 # sched: [3:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_permilpd:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vpermilpd {{.*#+}} xmm1 = mem[1,0] sched: [8:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; ZNVER1-NEXT: vpermilpd {{.*#+}} xmm0 = xmm0[1,0] sched: [1:0.50]
|
|
|
|
; ZNVER1-NEXT: vaddpd %xmm1, %xmm0, %xmm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = shufflevector <2 x double> %a0, <2 x double> undef, <2 x i32> <i32 1, i32 0>
|
|
|
|
%2 = load <2 x double>, <2 x double> *%a1, align 16
|
|
|
|
%3 = shufflevector <2 x double> %2, <2 x double> undef, <2 x i32> <i32 1, i32 0>
|
|
|
|
%4 = fadd <2 x double> %1, %3
|
|
|
|
ret <2 x double> %4
|
|
|
|
}
|
|
|
|
|
|
|
|
define <4 x double> @test_permilpd_ymm(<4 x double> %a0, <4 x double> *%a1) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_permilpd_ymm:
|
|
|
|
; GENERIC: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vpermilpd {{.*#+}} ymm0 = ymm0[1,0,2,3] sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: vpermilpd {{.*#+}} ymm1 = mem[1,0,2,3] sched: [8:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_permilpd_ymm:
|
|
|
|
; SANDY: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vpermilpd {{.*#+}} ymm0 = ymm0[1,0,2,3] sched: [1:1.00]
|
|
|
|
; SANDY-NEXT: vpermilpd {{.*#+}} ymm1 = mem[1,0,2,3] sched: [8:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_permilpd_ymm:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vpermilpd {{.*#+}} ymm0 = ymm0[1,0,2,3] sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vpermilpd {{.*#+}} ymm1 = mem[1,0,2,3] sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_permilpd_ymm:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vpermilpd {{.*#+}} ymm0 = ymm0[1,0,2,3] sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: vpermilpd {{.*#+}} ymm1 = mem[1,0,2,3] sched: [1:1.00]
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_permilpd_ymm:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vpermilpd {{.*#+}} ymm1 = mem[1,0,2,3] sched: [6:1.00]
|
|
|
|
; BTVER2-NEXT: vpermilpd {{.*#+}} ymm0 = ymm0[1,0,2,3] sched: [1:0.50]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_permilpd_ymm:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vpermilpd {{.*#+}} ymm1 = mem[1,0,2,3] sched: [8:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; ZNVER1-NEXT: vpermilpd {{.*#+}} ymm0 = ymm0[1,0,2,3] sched: [1:0.50]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = shufflevector <4 x double> %a0, <4 x double> undef, <4 x i32> <i32 1, i32 0, i32 2, i32 3>
|
|
|
|
%2 = load <4 x double>, <4 x double> *%a1, align 32
|
|
|
|
%3 = shufflevector <4 x double> %2, <4 x double> undef, <4 x i32> <i32 1, i32 0, i32 2, i32 3>
|
|
|
|
%4 = fadd <4 x double> %1, %3
|
|
|
|
ret <4 x double> %4
|
|
|
|
}
|
|
|
|
|
|
|
|
define <4 x float> @test_permilps(<4 x float> %a0, <4 x float> *%a1) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_permilps:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vpermilps {{.*#+}} xmm0 = xmm0[3,2,1,0] sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: vpermilps {{.*#+}} xmm1 = mem[3,2,1,0] sched: [7:1.00]
|
|
|
|
; GENERIC-NEXT: vaddps %xmm1, %xmm0, %xmm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_permilps:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vpermilps {{.*#+}} xmm0 = xmm0[3,2,1,0] sched: [1:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vpermilps {{.*#+}} xmm1 = mem[3,2,1,0] sched: [7:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vaddps %xmm1, %xmm0, %xmm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_permilps:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vpermilps {{.*#+}} xmm0 = xmm0[3,2,1,0] sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vpermilps {{.*#+}} xmm1 = mem[3,2,1,0] sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vaddps %xmm1, %xmm0, %xmm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_permilps:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vpermilps {{.*#+}} xmm0 = xmm0[3,2,1,0] sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: vpermilps {{.*#+}} xmm1 = mem[3,2,1,0] sched: [1:1.00]
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vaddps %xmm1, %xmm0, %xmm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_permilps:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vpermilps {{.*#+}} xmm1 = mem[3,2,1,0] sched: [6:1.00]
|
|
|
|
; BTVER2-NEXT: vpermilps {{.*#+}} xmm0 = xmm0[3,2,1,0] sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vaddps %xmm1, %xmm0, %xmm0 # sched: [3:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_permilps:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vpermilps {{.*#+}} xmm1 = mem[3,2,1,0] sched: [8:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; ZNVER1-NEXT: vpermilps {{.*#+}} xmm0 = xmm0[3,2,1,0] sched: [1:0.50]
|
|
|
|
; ZNVER1-NEXT: vaddps %xmm1, %xmm0, %xmm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = shufflevector <4 x float> %a0, <4 x float> undef, <4 x i32> <i32 3, i32 2, i32 1, i32 0>
|
|
|
|
%2 = load <4 x float>, <4 x float> *%a1, align 16
|
|
|
|
%3 = shufflevector <4 x float> %2, <4 x float> undef, <4 x i32> <i32 3, i32 2, i32 1, i32 0>
|
|
|
|
%4 = fadd <4 x float> %1, %3
|
|
|
|
ret <4 x float> %4
|
|
|
|
}
|
|
|
|
|
|
|
|
define <8 x float> @test_permilps_ymm(<8 x float> %a0, <8 x float> *%a1) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_permilps_ymm:
|
|
|
|
; GENERIC: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vpermilps {{.*#+}} ymm0 = ymm0[3,2,1,0,7,6,5,4] sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: vpermilps {{.*#+}} ymm1 = mem[3,2,1,0,7,6,5,4] sched: [8:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_permilps_ymm:
|
|
|
|
; SANDY: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vpermilps {{.*#+}} ymm0 = ymm0[3,2,1,0,7,6,5,4] sched: [1:1.00]
|
|
|
|
; SANDY-NEXT: vpermilps {{.*#+}} ymm1 = mem[3,2,1,0,7,6,5,4] sched: [8:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_permilps_ymm:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vpermilps {{.*#+}} ymm0 = ymm0[3,2,1,0,7,6,5,4] sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vpermilps {{.*#+}} ymm1 = mem[3,2,1,0,7,6,5,4] sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_permilps_ymm:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vpermilps {{.*#+}} ymm0 = ymm0[3,2,1,0,7,6,5,4] sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: vpermilps {{.*#+}} ymm1 = mem[3,2,1,0,7,6,5,4] sched: [1:1.00]
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_permilps_ymm:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vpermilps {{.*#+}} ymm1 = mem[3,2,1,0,7,6,5,4] sched: [6:1.00]
|
|
|
|
; BTVER2-NEXT: vpermilps {{.*#+}} ymm0 = ymm0[3,2,1,0,7,6,5,4] sched: [1:0.50]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_permilps_ymm:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vpermilps {{.*#+}} ymm1 = mem[3,2,1,0,7,6,5,4] sched: [8:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
; ZNVER1-NEXT: vpermilps {{.*#+}} ymm0 = ymm0[3,2,1,0,7,6,5,4] sched: [1:0.50]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = shufflevector <8 x float> %a0, <8 x float> undef, <8 x i32> <i32 3, i32 2, i32 1, i32 0, i32 7, i32 6, i32 5, i32 4>
|
|
|
|
%2 = load <8 x float>, <8 x float> *%a1, align 32
|
|
|
|
%3 = shufflevector <8 x float> %2, <8 x float> undef, <8 x i32> <i32 3, i32 2, i32 1, i32 0, i32 7, i32 6, i32 5, i32 4>
|
|
|
|
%4 = fadd <8 x float> %1, %3
|
|
|
|
ret <8 x float> %4
|
|
|
|
}
|
|
|
|
|
|
|
|
define <2 x double> @test_permilvarpd(<2 x double> %a0, <2 x i64> %a1, <2 x i64> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_permilvarpd:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vpermilpd %xmm1, %xmm0, %xmm0 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vpermilpd (%rdi), %xmm0, %xmm0 # sched: [7:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_permilvarpd:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vpermilpd %xmm1, %xmm0, %xmm0 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vpermilpd (%rdi), %xmm0, %xmm0 # sched: [7:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_permilvarpd:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vpermilpd %xmm1, %xmm0, %xmm0 # sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vpermilpd (%rdi), %xmm0, %xmm0 # sched: [1:1.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_permilvarpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vpermilpd %xmm1, %xmm0, %xmm0 # sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: vpermilpd (%rdi), %xmm0, %xmm0 # sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_permilvarpd:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vpermilpd %xmm1, %xmm0, %xmm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vpermilpd (%rdi), %xmm0, %xmm0 # sched: [6:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_permilvarpd:
|
|
|
|
; ZNVER1: # BB#0:
|
|
|
|
; ZNVER1-NEXT: vpermilpd %xmm1, %xmm0, %xmm0 # sched: [1:0.50]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vpermilpd (%rdi), %xmm0, %xmm0 # sched: [8:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call <2 x double> @llvm.x86.avx.vpermilvar.pd(<2 x double> %a0, <2 x i64> %a1)
|
|
|
|
%2 = load <2 x i64>, <2 x i64> *%a2, align 16
|
|
|
|
%3 = call <2 x double> @llvm.x86.avx.vpermilvar.pd(<2 x double> %1, <2 x i64> %2)
|
|
|
|
ret <2 x double> %3
|
|
|
|
}
|
|
|
|
declare <2 x double> @llvm.x86.avx.vpermilvar.pd(<2 x double>, <2 x i64>) nounwind readnone
|
|
|
|
|
|
|
|
define <4 x double> @test_permilvarpd_ymm(<4 x double> %a0, <4 x i64> %a1, <4 x i64> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_permilvarpd_ymm:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vpermilpd %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vpermilpd (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_permilvarpd_ymm:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vpermilpd %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vpermilpd (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_permilvarpd_ymm:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vpermilpd %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vpermilpd (%rdi), %ymm0, %ymm0 # sched: [1:1.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_permilvarpd_ymm:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vpermilpd %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: vpermilpd (%rdi), %ymm0, %ymm0 # sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_permilvarpd_ymm:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vpermilpd %ymm1, %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vpermilpd (%rdi), %ymm0, %ymm0 # sched: [6:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_permilvarpd_ymm:
|
|
|
|
; ZNVER1: # BB#0:
|
|
|
|
; ZNVER1-NEXT: vpermilpd %ymm1, %ymm0, %ymm0 # sched: [1:0.50]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vpermilpd (%rdi), %ymm0, %ymm0 # sched: [8:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call <4 x double> @llvm.x86.avx.vpermilvar.pd.256(<4 x double> %a0, <4 x i64> %a1)
|
|
|
|
%2 = load <4 x i64>, <4 x i64> *%a2, align 32
|
|
|
|
%3 = call <4 x double> @llvm.x86.avx.vpermilvar.pd.256(<4 x double> %1, <4 x i64> %2)
|
|
|
|
ret <4 x double> %3
|
|
|
|
}
|
|
|
|
declare <4 x double> @llvm.x86.avx.vpermilvar.pd.256(<4 x double>, <4 x i64>) nounwind readnone
|
|
|
|
|
|
|
|
define <4 x float> @test_permilvarps(<4 x float> %a0, <4 x i32> %a1, <4 x i32> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_permilvarps:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vpermilps %xmm1, %xmm0, %xmm0 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vpermilps (%rdi), %xmm0, %xmm0 # sched: [7:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_permilvarps:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vpermilps %xmm1, %xmm0, %xmm0 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vpermilps (%rdi), %xmm0, %xmm0 # sched: [7:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_permilvarps:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vpermilps %xmm1, %xmm0, %xmm0 # sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vpermilps (%rdi), %xmm0, %xmm0 # sched: [1:1.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_permilvarps:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vpermilps %xmm1, %xmm0, %xmm0 # sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: vpermilps (%rdi), %xmm0, %xmm0 # sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_permilvarps:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vpermilps %xmm1, %xmm0, %xmm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vpermilps (%rdi), %xmm0, %xmm0 # sched: [6:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_permilvarps:
|
|
|
|
; ZNVER1: # BB#0:
|
|
|
|
; ZNVER1-NEXT: vpermilps %xmm1, %xmm0, %xmm0 # sched: [1:0.50]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vpermilps (%rdi), %xmm0, %xmm0 # sched: [8:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call <4 x float> @llvm.x86.avx.vpermilvar.ps(<4 x float> %a0, <4 x i32> %a1)
|
|
|
|
%2 = load <4 x i32>, <4 x i32> *%a2, align 16
|
|
|
|
%3 = call <4 x float> @llvm.x86.avx.vpermilvar.ps(<4 x float> %1, <4 x i32> %2)
|
|
|
|
ret <4 x float> %3
|
|
|
|
}
|
|
|
|
declare <4 x float> @llvm.x86.avx.vpermilvar.ps(<4 x float>, <4 x i32>) nounwind readnone
|
|
|
|
|
|
|
|
define <8 x float> @test_permilvarps_ymm(<8 x float> %a0, <8 x i32> %a1, <8 x i32> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_permilvarps_ymm:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vpermilps %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vpermilps (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_permilvarps_ymm:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vpermilps %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vpermilps (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_permilvarps_ymm:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vpermilps %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vpermilps (%rdi), %ymm0, %ymm0 # sched: [1:1.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_permilvarps_ymm:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vpermilps %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: vpermilps (%rdi), %ymm0, %ymm0 # sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_permilvarps_ymm:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vpermilps %ymm1, %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vpermilps (%rdi), %ymm0, %ymm0 # sched: [6:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_permilvarps_ymm:
|
|
|
|
; ZNVER1: # BB#0:
|
|
|
|
; ZNVER1-NEXT: vpermilps %ymm1, %ymm0, %ymm0 # sched: [1:0.50]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vpermilps (%rdi), %ymm0, %ymm0 # sched: [8:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call <8 x float> @llvm.x86.avx.vpermilvar.ps.256(<8 x float> %a0, <8 x i32> %a1)
|
|
|
|
%2 = load <8 x i32>, <8 x i32> *%a2, align 32
|
|
|
|
%3 = call <8 x float> @llvm.x86.avx.vpermilvar.ps.256(<8 x float> %1, <8 x i32> %2)
|
|
|
|
ret <8 x float> %3
|
|
|
|
}
|
|
|
|
declare <8 x float> @llvm.x86.avx.vpermilvar.ps.256(<8 x float>, <8 x i32>) nounwind readnone
|
|
|
|
|
2017-04-24 06:08:17 +08:00
|
|
|
define <8 x float> @test_rcpps(<8 x float> %a0, <8 x float> *%a1) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_rcpps:
|
|
|
|
; GENERIC: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vrcpps (%rdi), %ymm1 # sched: [14:2.00]
|
|
|
|
; GENERIC-NEXT: vrcpps %ymm0, %ymm0 # sched: [7:2.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-LABEL: test_rcpps:
|
|
|
|
; SANDY: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vrcpps (%rdi), %ymm1 # sched: [14:2.00]
|
|
|
|
; SANDY-NEXT: vrcpps %ymm0, %ymm0 # sched: [7:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_rcpps:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vrcpps (%rdi), %ymm1 # sched: [11:2.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vrcpps %ymm0, %ymm0 # sched: [11:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; HASWELL-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_rcpps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vrcpps %ymm0, %ymm0 # sched: [4:1.00]
|
|
|
|
; SKYLAKE-NEXT: vrcpps (%rdi), %ymm1 # sched: [4:1.00]
|
|
|
|
; SKYLAKE-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-LABEL: test_rcpps:
|
|
|
|
; BTVER2: # BB#0:
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vrcpps (%rdi), %ymm1 # sched: [7:2.00]
|
|
|
|
; BTVER2-NEXT: vrcpps %ymm0, %ymm0 # sched: [2:2.00]
|
|
|
|
; BTVER2-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_rcpps:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vrcpps (%rdi), %ymm1 # sched: [12:0.50]
|
|
|
|
; ZNVER1-NEXT: vrcpps %ymm0, %ymm0 # sched: [5:0.50]
|
|
|
|
; ZNVER1-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 06:08:17 +08:00
|
|
|
%1 = call <8 x float> @llvm.x86.avx.rcp.ps.256(<8 x float> %a0)
|
|
|
|
%2 = load <8 x float>, <8 x float> *%a1, align 32
|
|
|
|
%3 = call <8 x float> @llvm.x86.avx.rcp.ps.256(<8 x float> %2)
|
|
|
|
%4 = fadd <8 x float> %1, %3
|
|
|
|
ret <8 x float> %4
|
|
|
|
}
|
|
|
|
declare <8 x float> @llvm.x86.avx.rcp.ps.256(<8 x float>) nounwind readnone
|
|
|
|
|
|
|
|
define <4 x double> @test_roundpd(<4 x double> %a0, <4 x double> *%a1) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_roundpd:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vroundpd $7, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vroundpd $7, (%rdi), %ymm1 # sched: [10:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-LABEL: test_roundpd:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vroundpd $7, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vroundpd $7, (%rdi), %ymm1 # sched: [10:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_roundpd:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vroundpd $7, %ymm0, %ymm0 # sched: [5:1.25]
|
|
|
|
; HASWELL-NEXT: vroundpd $7, (%rdi), %ymm1 # sched: [6:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; HASWELL-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_roundpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vroundpd $7, %ymm0, %ymm0 # sched: [8:0.67]
|
|
|
|
; SKYLAKE-NEXT: vroundpd $7, (%rdi), %ymm1 # sched: [8:0.67]
|
|
|
|
; SKYLAKE-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-LABEL: test_roundpd:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vroundpd $7, (%rdi), %ymm1 # sched: [8:1.00]
|
|
|
|
; BTVER2-NEXT: vroundpd $7, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_roundpd:
|
|
|
|
; ZNVER1: # BB#0:
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vroundpd $7, (%rdi), %ymm1 # sched: [11:1.00]
|
|
|
|
; ZNVER1-NEXT: vroundpd $7, %ymm0, %ymm0 # sched: [4:1.00]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 06:08:17 +08:00
|
|
|
%1 = call <4 x double> @llvm.x86.avx.round.pd.256(<4 x double> %a0, i32 7)
|
|
|
|
%2 = load <4 x double>, <4 x double> *%a1, align 32
|
|
|
|
%3 = call <4 x double> @llvm.x86.avx.round.pd.256(<4 x double> %2, i32 7)
|
|
|
|
%4 = fadd <4 x double> %1, %3
|
|
|
|
ret <4 x double> %4
|
|
|
|
}
|
|
|
|
declare <4 x double> @llvm.x86.avx.round.pd.256(<4 x double>, i32) nounwind readnone
|
|
|
|
|
|
|
|
define <8 x float> @test_roundps(<8 x float> %a0, <8 x float> *%a1) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_roundps:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vroundps $7, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vroundps $7, (%rdi), %ymm1 # sched: [10:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-LABEL: test_roundps:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vroundps $7, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vroundps $7, (%rdi), %ymm1 # sched: [10:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_roundps:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vroundps $7, %ymm0, %ymm0 # sched: [5:1.25]
|
|
|
|
; HASWELL-NEXT: vroundps $7, (%rdi), %ymm1 # sched: [6:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; HASWELL-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_roundps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vroundps $7, %ymm0, %ymm0 # sched: [8:0.67]
|
|
|
|
; SKYLAKE-NEXT: vroundps $7, (%rdi), %ymm1 # sched: [8:0.67]
|
|
|
|
; SKYLAKE-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-LABEL: test_roundps:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vroundps $7, (%rdi), %ymm1 # sched: [8:1.00]
|
|
|
|
; BTVER2-NEXT: vroundps $7, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_roundps:
|
|
|
|
; ZNVER1: # BB#0:
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vroundps $7, (%rdi), %ymm1 # sched: [11:1.00]
|
|
|
|
; ZNVER1-NEXT: vroundps $7, %ymm0, %ymm0 # sched: [4:1.00]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 06:08:17 +08:00
|
|
|
%1 = call <8 x float> @llvm.x86.avx.round.ps.256(<8 x float> %a0, i32 7)
|
|
|
|
%2 = load <8 x float>, <8 x float> *%a1, align 32
|
|
|
|
%3 = call <8 x float> @llvm.x86.avx.round.ps.256(<8 x float> %2, i32 7)
|
|
|
|
%4 = fadd <8 x float> %1, %3
|
|
|
|
ret <8 x float> %4
|
|
|
|
}
|
|
|
|
declare <8 x float> @llvm.x86.avx.round.ps.256(<8 x float>, i32) nounwind readnone
|
|
|
|
|
|
|
|
define <8 x float> @test_rsqrtps(<8 x float> %a0, <8 x float> *%a1) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_rsqrtps:
|
|
|
|
; GENERIC: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vrsqrtps (%rdi), %ymm1 # sched: [14:2.00]
|
|
|
|
; GENERIC-NEXT: vrsqrtps %ymm0, %ymm0 # sched: [7:2.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-LABEL: test_rsqrtps:
|
|
|
|
; SANDY: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vrsqrtps (%rdi), %ymm1 # sched: [14:2.00]
|
|
|
|
; SANDY-NEXT: vrsqrtps %ymm0, %ymm0 # sched: [7:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_rsqrtps:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vrsqrtps (%rdi), %ymm1 # sched: [11:2.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vrsqrtps %ymm0, %ymm0 # sched: [11:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; HASWELL-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_rsqrtps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vrsqrtps %ymm0, %ymm0 # sched: [4:1.00]
|
|
|
|
; SKYLAKE-NEXT: vrsqrtps (%rdi), %ymm1 # sched: [4:1.00]
|
|
|
|
; SKYLAKE-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-LABEL: test_rsqrtps:
|
|
|
|
; BTVER2: # BB#0:
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vrsqrtps (%rdi), %ymm1 # sched: [7:2.00]
|
|
|
|
; BTVER2-NEXT: vrsqrtps %ymm0, %ymm0 # sched: [2:2.00]
|
|
|
|
; BTVER2-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_rsqrtps:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vrsqrtps (%rdi), %ymm1 # sched: [12:0.50]
|
|
|
|
; ZNVER1-NEXT: vrsqrtps %ymm0, %ymm0 # sched: [5:0.50]
|
|
|
|
; ZNVER1-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 06:08:17 +08:00
|
|
|
%1 = call <8 x float> @llvm.x86.avx.rsqrt.ps.256(<8 x float> %a0)
|
|
|
|
%2 = load <8 x float>, <8 x float> *%a1, align 32
|
|
|
|
%3 = call <8 x float> @llvm.x86.avx.rsqrt.ps.256(<8 x float> %2)
|
|
|
|
%4 = fadd <8 x float> %1, %3
|
|
|
|
ret <8 x float> %4
|
|
|
|
}
|
|
|
|
declare <8 x float> @llvm.x86.avx.rsqrt.ps.256(<8 x float>) nounwind readnone
|
|
|
|
|
2017-04-24 22:26:30 +08:00
|
|
|
define <4 x double> @test_shufpd(<4 x double> %a0, <4 x double> %a1, <4 x double> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_shufpd:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vshufpd {{.*#+}} ymm0 = ymm0[1],ymm1[0],ymm0[2],ymm1[3] sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: vshufpd {{.*#+}} ymm1 = ymm1[1],mem[0],ymm1[2],mem[3] sched: [8:1.00]
|
|
|
|
; GENERIC-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_shufpd:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vshufpd {{.*#+}} ymm0 = ymm0[1],ymm1[0],ymm0[2],ymm1[3] sched: [1:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vshufpd {{.*#+}} ymm1 = ymm1[1],mem[0],ymm1[2],mem[3] sched: [8:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_shufpd:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vshufpd {{.*#+}} ymm0 = ymm0[1],ymm1[0],ymm0[2],ymm1[3] sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vshufpd {{.*#+}} ymm1 = ymm1[1],mem[0],ymm1[2],mem[3] sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_shufpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vshufpd {{.*#+}} ymm0 = ymm0[1],ymm1[0],ymm0[2],ymm1[3] sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: vshufpd {{.*#+}} ymm1 = ymm1[1],mem[0],ymm1[2],mem[3] sched: [1:1.00]
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_shufpd:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vshufpd {{.*#+}} ymm0 = ymm0[1],ymm1[0],ymm0[2],ymm1[3] sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vshufpd {{.*#+}} ymm1 = ymm1[1],mem[0],ymm1[2],mem[3] sched: [6:1.00]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_shufpd:
|
|
|
|
; ZNVER1: # BB#0:
|
|
|
|
; ZNVER1-NEXT: vshufpd {{.*#+}} ymm0 = ymm0[1],ymm1[0],ymm0[2],ymm1[3] sched: [1:0.50]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vshufpd {{.*#+}} ymm1 = ymm1[1],mem[0],ymm1[2],mem[3] sched: [8:0.50]
|
|
|
|
; ZNVER1-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = shufflevector <4 x double> %a0, <4 x double> %a1, <4 x i32> <i32 1, i32 4, i32 2, i32 7>
|
|
|
|
%2 = load <4 x double>, <4 x double> *%a2, align 32
|
|
|
|
%3 = shufflevector <4 x double> %a1, <4 x double> %2, <4 x i32> <i32 1, i32 4, i32 2, i32 7>
|
|
|
|
%4 = fadd <4 x double> %1, %3
|
|
|
|
ret <4 x double> %4
|
|
|
|
}
|
|
|
|
|
|
|
|
define <8 x float> @test_shufps(<8 x float> %a0, <8 x float> %a1, <8 x float> *%a2) nounwind {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_shufps:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vshufps {{.*#+}} ymm0 = ymm0[0,0],ymm1[0,0],ymm0[4,4],ymm1[4,4] sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: vshufps {{.*#+}} ymm0 = ymm0[0,3],mem[0,0],ymm0[4,7],mem[4,4] sched: [8:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_shufps:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vshufps {{.*#+}} ymm0 = ymm0[0,0],ymm1[0,0],ymm0[4,4],ymm1[4,4] sched: [1:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vshufps {{.*#+}} ymm0 = ymm0[0,3],mem[0,0],ymm0[4,7],mem[4,4] sched: [8:1.00]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_shufps:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vshufps {{.*#+}} ymm0 = ymm0[0,0],ymm1[0,0],ymm0[4,4],ymm1[4,4] sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vshufps {{.*#+}} ymm0 = ymm0[0,3],mem[0,0],ymm0[4,7],mem[4,4] sched: [1:1.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_shufps:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vshufps {{.*#+}} ymm0 = ymm0[0,0],ymm1[0,0],ymm0[4,4],ymm1[4,4] sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: vshufps {{.*#+}} ymm0 = ymm0[0,3],mem[0,0],ymm0[4,7],mem[4,4] sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_shufps:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vshufps {{.*#+}} ymm0 = ymm0[0,0],ymm1[0,0],ymm0[4,4],ymm1[4,4] sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vshufps {{.*#+}} ymm0 = ymm0[0,3],mem[0,0],ymm0[4,7],mem[4,4] sched: [6:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_shufps:
|
|
|
|
; ZNVER1: # BB#0:
|
|
|
|
; ZNVER1-NEXT: vshufps {{.*#+}} ymm0 = ymm0[0,0],ymm1[0,0],ymm0[4,4],ymm1[4,4] sched: [1:0.50]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vshufps {{.*#+}} ymm0 = ymm0[0,3],mem[0,0],ymm0[4,7],mem[4,4] sched: [8:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = shufflevector <8 x float> %a0, <8 x float> %a1, <8 x i32> <i32 0, i32 0, i32 8, i32 8, i32 4, i32 4, i32 12, i32 12>
|
|
|
|
%2 = load <8 x float>, <8 x float> *%a2, align 32
|
|
|
|
%3 = shufflevector <8 x float> %1, <8 x float> %2, <8 x i32> <i32 0, i32 3, i32 8, i32 8, i32 4, i32 7, i32 12, i32 12>
|
|
|
|
ret <8 x float> %3
|
|
|
|
}
|
|
|
|
|
2017-04-24 06:08:17 +08:00
|
|
|
define <4 x double> @test_sqrtpd(<4 x double> %a0, <4 x double> *%a1) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_sqrtpd:
|
|
|
|
; GENERIC: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vsqrtpd (%rdi), %ymm1 # sched: [52:2.00]
|
|
|
|
; GENERIC-NEXT: vsqrtpd %ymm0, %ymm0 # sched: [45:2.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-LABEL: test_sqrtpd:
|
|
|
|
; SANDY: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vsqrtpd (%rdi), %ymm1 # sched: [52:2.00]
|
|
|
|
; SANDY-NEXT: vsqrtpd %ymm0, %ymm0 # sched: [45:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_sqrtpd:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vsqrtpd (%rdi), %ymm1 # sched: [35:2.00]
|
|
|
|
; HASWELL-NEXT: vsqrtpd %ymm0, %ymm0 # sched: [35:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; HASWELL-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_sqrtpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vsqrtpd %ymm0, %ymm0 # sched: [18:1.00]
|
|
|
|
; SKYLAKE-NEXT: vsqrtpd (%rdi), %ymm1 # sched: [18:1.00]
|
|
|
|
; SKYLAKE-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-LABEL: test_sqrtpd:
|
|
|
|
; BTVER2: # BB#0:
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vsqrtpd (%rdi), %ymm1 # sched: [59:54.00]
|
|
|
|
; BTVER2-NEXT: vsqrtpd %ymm0, %ymm0 # sched: [54:54.00]
|
|
|
|
; BTVER2-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_sqrtpd:
|
|
|
|
; ZNVER1: # BB#0:
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vsqrtpd (%rdi), %ymm1 # sched: [47:47.00]
|
|
|
|
; ZNVER1-NEXT: vsqrtpd %ymm0, %ymm0 # sched: [40:40.00]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 06:08:17 +08:00
|
|
|
%1 = call <4 x double> @llvm.x86.avx.sqrt.pd.256(<4 x double> %a0)
|
|
|
|
%2 = load <4 x double>, <4 x double> *%a1, align 32
|
|
|
|
%3 = call <4 x double> @llvm.x86.avx.sqrt.pd.256(<4 x double> %2)
|
|
|
|
%4 = fadd <4 x double> %1, %3
|
|
|
|
ret <4 x double> %4
|
|
|
|
}
|
|
|
|
declare <4 x double> @llvm.x86.avx.sqrt.pd.256(<4 x double>) nounwind readnone
|
|
|
|
|
|
|
|
define <8 x float> @test_sqrtps(<8 x float> %a0, <8 x float> *%a1) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_sqrtps:
|
|
|
|
; GENERIC: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vsqrtps (%rdi), %ymm1 # sched: [36:2.00]
|
|
|
|
; GENERIC-NEXT: vsqrtps %ymm0, %ymm0 # sched: [29:2.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-LABEL: test_sqrtps:
|
|
|
|
; SANDY: # BB#0:
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vsqrtps (%rdi), %ymm1 # sched: [36:2.00]
|
|
|
|
; SANDY-NEXT: vsqrtps %ymm0, %ymm0 # sched: [29:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_sqrtps:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vsqrtps (%rdi), %ymm1 # sched: [21:2.00]
|
|
|
|
; HASWELL-NEXT: vsqrtps %ymm0, %ymm0 # sched: [21:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; HASWELL-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_sqrtps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vsqrtps %ymm0, %ymm0 # sched: [12:1.00]
|
|
|
|
; SKYLAKE-NEXT: vsqrtps (%rdi), %ymm1 # sched: [12:1.00]
|
|
|
|
; SKYLAKE-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-LABEL: test_sqrtps:
|
|
|
|
; BTVER2: # BB#0:
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vsqrtps (%rdi), %ymm1 # sched: [47:42.00]
|
|
|
|
; BTVER2-NEXT: vsqrtps %ymm0, %ymm0 # sched: [42:42.00]
|
|
|
|
; BTVER2-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_sqrtps:
|
|
|
|
; ZNVER1: # BB#0:
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vsqrtps (%rdi), %ymm1 # sched: [35:35.00]
|
|
|
|
; ZNVER1-NEXT: vsqrtps %ymm0, %ymm0 # sched: [28:28.00]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vaddps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 06:08:17 +08:00
|
|
|
%1 = call <8 x float> @llvm.x86.avx.sqrt.ps.256(<8 x float> %a0)
|
|
|
|
%2 = load <8 x float>, <8 x float> *%a1, align 32
|
|
|
|
%3 = call <8 x float> @llvm.x86.avx.sqrt.ps.256(<8 x float> %2)
|
|
|
|
%4 = fadd <8 x float> %1, %3
|
|
|
|
ret <8 x float> %4
|
|
|
|
}
|
|
|
|
declare <8 x float> @llvm.x86.avx.sqrt.ps.256(<8 x float>) nounwind readnone
|
|
|
|
|
|
|
|
define <4 x double> @test_subpd(<4 x double> %a0, <4 x double> %a1, <4 x double> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_subpd:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vsubpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: vsubpd (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-LABEL: test_subpd:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vsubpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vsubpd (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_subpd:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vsubpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vsubpd (%rdi), %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_subpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vsubpd %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
|
|
|
; SKYLAKE-NEXT: vsubpd (%rdi), %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-LABEL: test_subpd:
|
|
|
|
; BTVER2: # BB#0:
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vsubpd %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
|
|
|
; BTVER2-NEXT: vsubpd (%rdi), %ymm0, %ymm0 # sched: [8:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_subpd:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vsubpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; ZNVER1-NEXT: vsubpd (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 06:08:17 +08:00
|
|
|
%1 = fsub <4 x double> %a0, %a1
|
|
|
|
%2 = load <4 x double>, <4 x double> *%a2, align 32
|
|
|
|
%3 = fsub <4 x double> %1, %2
|
|
|
|
ret <4 x double> %3
|
|
|
|
}
|
|
|
|
|
|
|
|
define <8 x float> @test_subps(<8 x float> %a0, <8 x float> %a1, <8 x float> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_subps:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vsubps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: vsubps (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-LABEL: test_subps:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vsubps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vsubps (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_subps:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vsubps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vsubps (%rdi), %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_subps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vsubps %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
|
|
|
; SKYLAKE-NEXT: vsubps (%rdi), %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-LABEL: test_subps:
|
|
|
|
; BTVER2: # BB#0:
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vsubps %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
|
|
|
; BTVER2-NEXT: vsubps (%rdi), %ymm0, %ymm0 # sched: [8:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_subps:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vsubps %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; ZNVER1-NEXT: vsubps (%rdi), %ymm0, %ymm0 # sched: [10:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 06:08:17 +08:00
|
|
|
%1 = fsub <8 x float> %a0, %a1
|
|
|
|
%2 = load <8 x float>, <8 x float> *%a2, align 32
|
|
|
|
%3 = fsub <8 x float> %1, %2
|
|
|
|
ret <8 x float> %3
|
|
|
|
}
|
|
|
|
|
2017-04-24 22:26:30 +08:00
|
|
|
define i32 @test_testpd(<2 x double> %a0, <2 x double> %a1, <2 x double> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_testpd:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: xorl %eax, %eax # sched: [1:0.33]
|
|
|
|
; GENERIC-NEXT: vtestpd %xmm1, %xmm0 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: setb %al # sched: [1:0.50]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vtestpd (%rdi), %xmm0 # sched: [7:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: adcl $0, %eax # sched: [2:0.67]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_testpd:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: xorl %eax, %eax # sched: [1:0.33]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vtestpd %xmm1, %xmm0 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: setb %al # sched: [1:0.50]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vtestpd (%rdi), %xmm0 # sched: [7:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: adcl $0, %eax # sched: [2:0.67]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_testpd:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: xorl %eax, %eax # sched: [1:0.25]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vtestpd %xmm1, %xmm0 # sched: [1:1.00]
|
2017-06-28 19:23:31 +08:00
|
|
|
; HASWELL-NEXT: setb %al # sched: [1:0.50]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vtestpd (%rdi), %xmm0 # sched: [1:1.00]
|
2017-06-28 19:23:31 +08:00
|
|
|
; HASWELL-NEXT: adcl $0, %eax # sched: [2:0.50]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_testpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: xorl %eax, %eax # sched: [1:0.25]
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vtestpd %xmm1, %xmm0 # sched: [2:1.00]
|
|
|
|
; SKYLAKE-NEXT: setb %al # sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: vtestpd (%rdi), %xmm0 # sched: [2:1.00]
|
|
|
|
; SKYLAKE-NEXT: adcl $0, %eax # sched: [1:1.00]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_testpd:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: xorl %eax, %eax # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vtestpd %xmm1, %xmm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: setb %al # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vtestpd (%rdi), %xmm0 # sched: [6:1.00]
|
|
|
|
; BTVER2-NEXT: adcl $0, %eax # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_testpd:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: xorl %eax, %eax # sched: [1:0.25]
|
|
|
|
; ZNVER1-NEXT: vtestpd %xmm1, %xmm0 # sched: [1:0.25]
|
|
|
|
; ZNVER1-NEXT: setb %al # sched: [1:0.25]
|
|
|
|
; ZNVER1-NEXT: vtestpd (%rdi), %xmm0 # sched: [8:0.50]
|
|
|
|
; ZNVER1-NEXT: adcl $0, %eax # sched: [1:0.25]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call i32 @llvm.x86.avx.vtestc.pd(<2 x double> %a0, <2 x double> %a1)
|
|
|
|
%2 = load <2 x double>, <2 x double> *%a2, align 16
|
|
|
|
%3 = call i32 @llvm.x86.avx.vtestc.pd(<2 x double> %a0, <2 x double> %2)
|
|
|
|
%4 = add i32 %1, %3
|
|
|
|
ret i32 %4
|
|
|
|
}
|
|
|
|
declare i32 @llvm.x86.avx.vtestc.pd(<2 x double>, <2 x double>) nounwind readnone
|
|
|
|
|
|
|
|
define i32 @test_testpd_ymm(<4 x double> %a0, <4 x double> %a1, <4 x double> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_testpd_ymm:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: xorl %eax, %eax # sched: [1:0.33]
|
|
|
|
; GENERIC-NEXT: vtestpd %ymm1, %ymm0 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: setb %al # sched: [1:0.50]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vtestpd (%rdi), %ymm0 # sched: [8:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: adcl $0, %eax # sched: [2:0.67]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vzeroupper
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_testpd_ymm:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: xorl %eax, %eax # sched: [1:0.33]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vtestpd %ymm1, %ymm0 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: setb %al # sched: [1:0.50]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vtestpd (%rdi), %ymm0 # sched: [8:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: adcl $0, %eax # sched: [2:0.67]
|
2017-07-27 02:55:14 +08:00
|
|
|
; SANDY-NEXT: vzeroupper
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_testpd_ymm:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: xorl %eax, %eax # sched: [1:0.25]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vtestpd %ymm1, %ymm0 # sched: [1:1.00]
|
2017-06-28 19:23:31 +08:00
|
|
|
; HASWELL-NEXT: setb %al # sched: [1:0.50]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vtestpd (%rdi), %ymm0 # sched: [1:1.00]
|
2017-06-28 19:23:31 +08:00
|
|
|
; HASWELL-NEXT: adcl $0, %eax # sched: [2:0.50]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vzeroupper # sched: [4:1.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_testpd_ymm:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: xorl %eax, %eax # sched: [1:0.25]
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vtestpd %ymm1, %ymm0 # sched: [2:1.00]
|
|
|
|
; SKYLAKE-NEXT: setb %al # sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: vtestpd (%rdi), %ymm0 # sched: [2:1.00]
|
|
|
|
; SKYLAKE-NEXT: adcl $0, %eax # sched: [1:1.00]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: vzeroupper # sched: [4:1.00]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_testpd_ymm:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: xorl %eax, %eax # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vtestpd %ymm1, %ymm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: setb %al # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vtestpd (%rdi), %ymm0 # sched: [6:1.00]
|
|
|
|
; BTVER2-NEXT: adcl $0, %eax # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_testpd_ymm:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: xorl %eax, %eax # sched: [1:0.25]
|
|
|
|
; ZNVER1-NEXT: vtestpd %ymm1, %ymm0 # sched: [1:0.25]
|
|
|
|
; ZNVER1-NEXT: setb %al # sched: [1:0.25]
|
|
|
|
; ZNVER1-NEXT: vtestpd (%rdi), %ymm0 # sched: [8:0.50]
|
|
|
|
; ZNVER1-NEXT: adcl $0, %eax # sched: [1:0.25]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vzeroupper # sched: [100:?]
|
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call i32 @llvm.x86.avx.vtestc.pd.256(<4 x double> %a0, <4 x double> %a1)
|
|
|
|
%2 = load <4 x double>, <4 x double> *%a2, align 32
|
|
|
|
%3 = call i32 @llvm.x86.avx.vtestc.pd.256(<4 x double> %a0, <4 x double> %2)
|
|
|
|
%4 = add i32 %1, %3
|
|
|
|
ret i32 %4
|
|
|
|
}
|
|
|
|
declare i32 @llvm.x86.avx.vtestc.pd.256(<4 x double>, <4 x double>) nounwind readnone
|
|
|
|
|
|
|
|
define i32 @test_testps(<4 x float> %a0, <4 x float> %a1, <4 x float> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_testps:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: xorl %eax, %eax # sched: [1:0.33]
|
|
|
|
; GENERIC-NEXT: vtestps %xmm1, %xmm0 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: setb %al # sched: [1:0.50]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vtestps (%rdi), %xmm0 # sched: [7:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: adcl $0, %eax # sched: [2:0.67]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_testps:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: xorl %eax, %eax # sched: [1:0.33]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vtestps %xmm1, %xmm0 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: setb %al # sched: [1:0.50]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vtestps (%rdi), %xmm0 # sched: [7:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: adcl $0, %eax # sched: [2:0.67]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_testps:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: xorl %eax, %eax # sched: [1:0.25]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vtestps %xmm1, %xmm0 # sched: [1:1.00]
|
2017-06-28 19:23:31 +08:00
|
|
|
; HASWELL-NEXT: setb %al # sched: [1:0.50]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vtestps (%rdi), %xmm0 # sched: [1:1.00]
|
2017-06-28 19:23:31 +08:00
|
|
|
; HASWELL-NEXT: adcl $0, %eax # sched: [2:0.50]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_testps:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: xorl %eax, %eax # sched: [1:0.25]
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vtestps %xmm1, %xmm0 # sched: [2:1.00]
|
|
|
|
; SKYLAKE-NEXT: setb %al # sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: vtestps (%rdi), %xmm0 # sched: [2:1.00]
|
|
|
|
; SKYLAKE-NEXT: adcl $0, %eax # sched: [1:1.00]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_testps:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: xorl %eax, %eax # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vtestps %xmm1, %xmm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: setb %al # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vtestps (%rdi), %xmm0 # sched: [6:1.00]
|
|
|
|
; BTVER2-NEXT: adcl $0, %eax # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_testps:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: xorl %eax, %eax # sched: [1:0.25]
|
|
|
|
; ZNVER1-NEXT: vtestps %xmm1, %xmm0 # sched: [1:0.25]
|
|
|
|
; ZNVER1-NEXT: setb %al # sched: [1:0.25]
|
|
|
|
; ZNVER1-NEXT: vtestps (%rdi), %xmm0 # sched: [8:0.50]
|
|
|
|
; ZNVER1-NEXT: adcl $0, %eax # sched: [1:0.25]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call i32 @llvm.x86.avx.vtestc.ps(<4 x float> %a0, <4 x float> %a1)
|
|
|
|
%2 = load <4 x float>, <4 x float> *%a2, align 16
|
|
|
|
%3 = call i32 @llvm.x86.avx.vtestc.ps(<4 x float> %a0, <4 x float> %2)
|
|
|
|
%4 = add i32 %1, %3
|
|
|
|
ret i32 %4
|
|
|
|
}
|
|
|
|
declare i32 @llvm.x86.avx.vtestc.ps(<4 x float>, <4 x float>) nounwind readnone
|
|
|
|
|
|
|
|
define i32 @test_testps_ymm(<8 x float> %a0, <8 x float> %a1, <8 x float> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_testps_ymm:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: xorl %eax, %eax # sched: [1:0.33]
|
|
|
|
; GENERIC-NEXT: vtestps %ymm1, %ymm0 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: setb %al # sched: [1:0.50]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vtestps (%rdi), %ymm0 # sched: [8:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: adcl $0, %eax # sched: [2:0.67]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vzeroupper
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_testps_ymm:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: xorl %eax, %eax # sched: [1:0.33]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vtestps %ymm1, %ymm0 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: setb %al # sched: [1:0.50]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vtestps (%rdi), %ymm0 # sched: [8:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: adcl $0, %eax # sched: [2:0.67]
|
2017-07-27 02:55:14 +08:00
|
|
|
; SANDY-NEXT: vzeroupper
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_testps_ymm:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: xorl %eax, %eax # sched: [1:0.25]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vtestps %ymm1, %ymm0 # sched: [1:1.00]
|
2017-06-28 19:23:31 +08:00
|
|
|
; HASWELL-NEXT: setb %al # sched: [1:0.50]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vtestps (%rdi), %ymm0 # sched: [1:1.00]
|
2017-06-28 19:23:31 +08:00
|
|
|
; HASWELL-NEXT: adcl $0, %eax # sched: [2:0.50]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vzeroupper # sched: [4:1.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_testps_ymm:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: xorl %eax, %eax # sched: [1:0.25]
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vtestps %ymm1, %ymm0 # sched: [2:1.00]
|
|
|
|
; SKYLAKE-NEXT: setb %al # sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: vtestps (%rdi), %ymm0 # sched: [2:1.00]
|
|
|
|
; SKYLAKE-NEXT: adcl $0, %eax # sched: [1:1.00]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: vzeroupper # sched: [4:1.00]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_testps_ymm:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: xorl %eax, %eax # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vtestps %ymm1, %ymm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: setb %al # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vtestps (%rdi), %ymm0 # sched: [6:1.00]
|
|
|
|
; BTVER2-NEXT: adcl $0, %eax # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_testps_ymm:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: xorl %eax, %eax # sched: [1:0.25]
|
|
|
|
; ZNVER1-NEXT: vtestps %ymm1, %ymm0 # sched: [1:0.25]
|
|
|
|
; ZNVER1-NEXT: setb %al # sched: [1:0.25]
|
|
|
|
; ZNVER1-NEXT: vtestps (%rdi), %ymm0 # sched: [8:0.50]
|
|
|
|
; ZNVER1-NEXT: adcl $0, %eax # sched: [1:0.25]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vzeroupper # sched: [100:?]
|
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = call i32 @llvm.x86.avx.vtestc.ps.256(<8 x float> %a0, <8 x float> %a1)
|
|
|
|
%2 = load <8 x float>, <8 x float> *%a2, align 32
|
|
|
|
%3 = call i32 @llvm.x86.avx.vtestc.ps.256(<8 x float> %a0, <8 x float> %2)
|
|
|
|
%4 = add i32 %1, %3
|
|
|
|
ret i32 %4
|
|
|
|
}
|
|
|
|
declare i32 @llvm.x86.avx.vtestc.ps.256(<8 x float>, <8 x float>) nounwind readnone
|
|
|
|
|
|
|
|
define <4 x double> @test_unpckhpd(<4 x double> %a0, <4 x double> %a1, <4 x double> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_unpckhpd:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vunpckhpd {{.*#+}} ymm0 = ymm0[1],ymm1[1],ymm0[3],ymm1[3] sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vunpckhpd {{.*#+}} ymm1 = ymm1[1],mem[1],ymm1[3],mem[3] sched: [8:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_unpckhpd:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vunpckhpd {{.*#+}} ymm0 = ymm0[1],ymm1[1],ymm0[3],ymm1[3] sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vunpckhpd {{.*#+}} ymm1 = ymm1[1],mem[1],ymm1[3],mem[3] sched: [8:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_unpckhpd:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vunpckhpd {{.*#+}} ymm0 = ymm0[1],ymm1[1],ymm0[3],ymm1[3] sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vunpckhpd {{.*#+}} ymm1 = ymm1[1],mem[1],ymm1[3],mem[3] sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_unpckhpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vunpckhpd {{.*#+}} ymm0 = ymm0[1],ymm1[1],ymm0[3],ymm1[3] sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: vunpckhpd {{.*#+}} ymm1 = ymm1[1],mem[1],ymm1[3],mem[3] sched: [1:1.00]
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_unpckhpd:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vunpckhpd {{.*#+}} ymm0 = ymm0[1],ymm1[1],ymm0[3],ymm1[3] sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vunpckhpd {{.*#+}} ymm1 = ymm1[1],mem[1],ymm1[3],mem[3] sched: [6:1.00]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_unpckhpd:
|
|
|
|
; ZNVER1: # BB#0:
|
|
|
|
; ZNVER1-NEXT: vunpckhpd {{.*#+}} ymm0 = ymm0[1],ymm1[1],ymm0[3],ymm1[3] sched: [1:0.50]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vunpckhpd {{.*#+}} ymm1 = ymm1[1],mem[1],ymm1[3],mem[3] sched: [8:0.50]
|
|
|
|
; ZNVER1-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = shufflevector <4 x double> %a0, <4 x double> %a1, <4 x i32> <i32 1, i32 5, i32 3, i32 7>
|
|
|
|
%2 = load <4 x double>, <4 x double> *%a2, align 32
|
|
|
|
%3 = shufflevector <4 x double> %a1, <4 x double> %2, <4 x i32> <i32 1, i32 5, i32 3, i32 7>
|
|
|
|
%4 = fadd <4 x double> %1, %3
|
|
|
|
ret <4 x double> %4
|
|
|
|
}
|
|
|
|
|
|
|
|
define <8 x float> @test_unpckhps(<8 x float> %a0, <8 x float> %a1, <8 x float> *%a2) nounwind {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_unpckhps:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vunpckhps {{.*#+}} ymm0 = ymm0[2],ymm1[2],ymm0[3],ymm1[3],ymm0[6],ymm1[6],ymm0[7],ymm1[7] sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vunpckhps {{.*#+}} ymm0 = ymm0[2],mem[2],ymm0[3],mem[3],ymm0[6],mem[6],ymm0[7],mem[7] sched: [8:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_unpckhps:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vunpckhps {{.*#+}} ymm0 = ymm0[2],ymm1[2],ymm0[3],ymm1[3],ymm0[6],ymm1[6],ymm0[7],ymm1[7] sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vunpckhps {{.*#+}} ymm0 = ymm0[2],mem[2],ymm0[3],mem[3],ymm0[6],mem[6],ymm0[7],mem[7] sched: [8:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_unpckhps:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vunpckhps {{.*#+}} ymm0 = ymm0[2],ymm1[2],ymm0[3],ymm1[3],ymm0[6],ymm1[6],ymm0[7],ymm1[7] sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vunpckhps {{.*#+}} ymm0 = ymm0[2],mem[2],ymm0[3],mem[3],ymm0[6],mem[6],ymm0[7],mem[7] sched: [1:1.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_unpckhps:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vunpckhps {{.*#+}} ymm0 = ymm0[2],ymm1[2],ymm0[3],ymm1[3],ymm0[6],ymm1[6],ymm0[7],ymm1[7] sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: vunpckhps {{.*#+}} ymm0 = ymm0[2],mem[2],ymm0[3],mem[3],ymm0[6],mem[6],ymm0[7],mem[7] sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_unpckhps:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vunpckhps {{.*#+}} ymm0 = ymm0[2],ymm1[2],ymm0[3],ymm1[3],ymm0[6],ymm1[6],ymm0[7],ymm1[7] sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vunpckhps {{.*#+}} ymm0 = ymm0[2],mem[2],ymm0[3],mem[3],ymm0[6],mem[6],ymm0[7],mem[7] sched: [6:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_unpckhps:
|
|
|
|
; ZNVER1: # BB#0:
|
|
|
|
; ZNVER1-NEXT: vunpckhps {{.*#+}} ymm0 = ymm0[2],ymm1[2],ymm0[3],ymm1[3],ymm0[6],ymm1[6],ymm0[7],ymm1[7] sched: [1:0.50]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vunpckhps {{.*#+}} ymm0 = ymm0[2],mem[2],ymm0[3],mem[3],ymm0[6],mem[6],ymm0[7],mem[7] sched: [8:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = shufflevector <8 x float> %a0, <8 x float> %a1, <8 x i32> <i32 2, i32 10, i32 3, i32 11, i32 6, i32 14, i32 7, i32 15>
|
|
|
|
%2 = load <8 x float>, <8 x float> *%a2, align 32
|
|
|
|
%3 = shufflevector <8 x float> %1, <8 x float> %2, <8 x i32> <i32 2, i32 10, i32 3, i32 11, i32 6, i32 14, i32 7, i32 15>
|
|
|
|
ret <8 x float> %3
|
|
|
|
}
|
|
|
|
|
|
|
|
define <4 x double> @test_unpcklpd(<4 x double> %a0, <4 x double> %a1, <4 x double> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_unpcklpd:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vunpcklpd {{.*#+}} ymm0 = ymm0[0],ymm1[0],ymm0[2],ymm1[2] sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: vunpcklpd {{.*#+}} ymm1 = ymm1[0],mem[0],ymm1[2],mem[2] sched: [8:1.00]
|
|
|
|
; GENERIC-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_unpcklpd:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vunpcklpd {{.*#+}} ymm0 = ymm0[0],ymm1[0],ymm0[2],ymm1[2] sched: [1:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vunpcklpd {{.*#+}} ymm1 = ymm1[0],mem[0],ymm1[2],mem[2] sched: [8:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_unpcklpd:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vunpcklpd {{.*#+}} ymm0 = ymm0[0],ymm1[0],ymm0[2],ymm1[2] sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vunpcklpd {{.*#+}} ymm1 = ymm1[0],mem[0],ymm1[2],mem[2] sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; HASWELL-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_unpcklpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vunpcklpd {{.*#+}} ymm0 = ymm0[0],ymm1[0],ymm0[2],ymm1[2] sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: vunpcklpd {{.*#+}} ymm1 = ymm1[0],mem[0],ymm1[2],mem[2] sched: [1:1.00]
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_unpcklpd:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vunpcklpd {{.*#+}} ymm0 = ymm0[0],ymm1[0],ymm0[2],ymm1[2] sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vunpcklpd {{.*#+}} ymm1 = ymm1[0],mem[0],ymm1[2],mem[2] sched: [6:1.00]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:2.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_unpcklpd:
|
|
|
|
; ZNVER1: # BB#0:
|
|
|
|
; ZNVER1-NEXT: vunpcklpd {{.*#+}} ymm0 = ymm0[0],ymm1[0],ymm0[2],ymm1[2] sched: [1:0.50]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vunpcklpd {{.*#+}} ymm1 = ymm1[0],mem[0],ymm1[2],mem[2] sched: [8:0.50]
|
|
|
|
; ZNVER1-NEXT: vaddpd %ymm1, %ymm0, %ymm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = shufflevector <4 x double> %a0, <4 x double> %a1, <4 x i32> <i32 0, i32 4, i32 2, i32 6>
|
|
|
|
%2 = load <4 x double>, <4 x double> *%a2, align 32
|
|
|
|
%3 = shufflevector <4 x double> %a1, <4 x double> %2, <4 x i32> <i32 0, i32 4, i32 2, i32 6>
|
|
|
|
%4 = fadd <4 x double> %1, %3
|
|
|
|
ret <4 x double> %4
|
|
|
|
}
|
|
|
|
|
|
|
|
define <8 x float> @test_unpcklps(<8 x float> %a0, <8 x float> %a1, <8 x float> *%a2) nounwind {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_unpcklps:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vunpcklps {{.*#+}} ymm0 = ymm0[0],ymm1[0],ymm0[1],ymm1[1],ymm0[4],ymm1[4],ymm0[5],ymm1[5] sched: [1:1.00]
|
|
|
|
; GENERIC-NEXT: vunpcklps {{.*#+}} ymm0 = ymm0[0],mem[0],ymm0[1],mem[1],ymm0[4],mem[4],ymm0[5],mem[5] sched: [8:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; SANDY-LABEL: test_unpcklps:
|
|
|
|
; SANDY: # BB#0:
|
|
|
|
; SANDY-NEXT: vunpcklps {{.*#+}} ymm0 = ymm0[0],ymm1[0],ymm0[1],ymm1[1],ymm0[4],ymm1[4],ymm0[5],ymm1[5] sched: [1:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vunpcklps {{.*#+}} ymm0 = ymm0[0],mem[0],ymm0[1],mem[1],ymm0[4],mem[4],ymm0[5],mem[5] sched: [8:1.00]
|
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_unpcklps:
|
|
|
|
; HASWELL: # BB#0:
|
|
|
|
; HASWELL-NEXT: vunpcklps {{.*#+}} ymm0 = ymm0[0],ymm1[0],ymm0[1],ymm1[1],ymm0[4],ymm1[4],ymm0[5],ymm1[5] sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vunpcklps {{.*#+}} ymm0 = ymm0[0],mem[0],ymm0[1],mem[1],ymm0[4],mem[4],ymm0[5],mem[5] sched: [1:1.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_unpcklps:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vunpcklps {{.*#+}} ymm0 = ymm0[0],ymm1[0],ymm0[1],ymm1[1],ymm0[4],ymm1[4],ymm0[5],ymm1[5] sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: vunpcklps {{.*#+}} ymm0 = ymm0[0],mem[0],ymm0[1],mem[1],ymm0[4],mem[4],ymm0[5],mem[5] sched: [1:1.00]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 22:26:30 +08:00
|
|
|
; BTVER2-LABEL: test_unpcklps:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vunpcklps {{.*#+}} ymm0 = ymm0[0],ymm1[0],ymm0[1],ymm1[1],ymm0[4],ymm1[4],ymm0[5],ymm1[5] sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vunpcklps {{.*#+}} ymm0 = ymm0[0],mem[0],ymm0[1],mem[1],ymm0[4],mem[4],ymm0[5],mem[5] sched: [6:1.00]
|
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_unpcklps:
|
|
|
|
; ZNVER1: # BB#0:
|
|
|
|
; ZNVER1-NEXT: vunpcklps {{.*#+}} ymm0 = ymm0[0],ymm1[0],ymm0[1],ymm1[1],ymm0[4],ymm1[4],ymm0[5],ymm1[5] sched: [1:0.50]
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vunpcklps {{.*#+}} ymm0 = ymm0[0],mem[0],ymm0[1],mem[1],ymm0[4],mem[4],ymm0[5],mem[5] sched: [8:0.50]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 22:26:30 +08:00
|
|
|
%1 = shufflevector <8 x float> %a0, <8 x float> %a1, <8 x i32> <i32 0, i32 8, i32 1, i32 9, i32 4, i32 12, i32 5, i32 13>
|
|
|
|
%2 = load <8 x float>, <8 x float> *%a2, align 32
|
|
|
|
%3 = shufflevector <8 x float> %1, <8 x float> %2, <8 x i32> <i32 0, i32 8, i32 1, i32 9, i32 4, i32 12, i32 5, i32 13>
|
|
|
|
ret <8 x float> %3
|
|
|
|
}
|
|
|
|
|
2017-04-24 06:08:17 +08:00
|
|
|
define <4 x double> @test_xorpd(<4 x double> %a0, <4 x double> %a1, <4 x double> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_xorpd:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vxorpd %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vxorpd (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-LABEL: test_xorpd:
|
|
|
|
; SANDY: # BB#0:
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vxorpd %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vxorpd (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_xorpd:
|
|
|
|
; HASWELL: # BB#0:
|
2017-06-28 19:23:31 +08:00
|
|
|
; HASWELL-NEXT: vxorpd %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vxorpd (%rdi), %ymm0, %ymm0 # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; HASWELL-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_xorpd:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vxorpd %ymm1, %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: vxorpd (%rdi), %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-LABEL: test_xorpd:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vxorpd %ymm1, %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vxorpd (%rdi), %ymm0, %ymm0 # sched: [6:1.00]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_xorpd:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vxorpd %ymm1, %ymm0, %ymm0 # sched: [1:0.25]
|
|
|
|
; ZNVER1-NEXT: vxorpd (%rdi), %ymm0, %ymm0 # sched: [8:0.50]
|
|
|
|
; ZNVER1-NEXT: vaddpd %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 06:08:17 +08:00
|
|
|
%1 = bitcast <4 x double> %a0 to <4 x i64>
|
|
|
|
%2 = bitcast <4 x double> %a1 to <4 x i64>
|
|
|
|
%3 = xor <4 x i64> %1, %2
|
|
|
|
%4 = load <4 x double>, <4 x double> *%a2, align 32
|
|
|
|
%5 = bitcast <4 x double> %4 to <4 x i64>
|
|
|
|
%6 = xor <4 x i64> %3, %5
|
|
|
|
%7 = bitcast <4 x i64> %6 to <4 x double>
|
|
|
|
%8 = fadd <4 x double> %a1, %7
|
|
|
|
ret <4 x double> %8
|
|
|
|
}
|
|
|
|
|
|
|
|
define <8 x float> @test_xorps(<8 x float> %a0, <8 x float> %a1, <8 x float> *%a2) {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_xorps:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vxorps %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; GENERIC-NEXT: vxorps (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-LABEL: test_xorps:
|
|
|
|
; SANDY: # BB#0:
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: vxorps %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
2017-08-13 21:59:24 +08:00
|
|
|
; SANDY-NEXT: vxorps (%rdi), %ymm0, %ymm0 # sched: [8:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; SANDY-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_xorps:
|
|
|
|
; HASWELL: # BB#0:
|
2017-06-28 19:23:31 +08:00
|
|
|
; HASWELL-NEXT: vxorps %ymm1, %ymm0, %ymm0 # sched: [1:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vxorps (%rdi), %ymm0, %ymm0 # sched: [1:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; HASWELL-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_xorps:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vxorps %ymm1, %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: vxorps (%rdi), %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; SKYLAKE-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [4:0.50]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-LABEL: test_xorps:
|
|
|
|
; BTVER2: # BB#0:
|
|
|
|
; BTVER2-NEXT: vxorps %ymm1, %ymm0, %ymm0 # sched: [1:0.50]
|
|
|
|
; BTVER2-NEXT: vxorps (%rdi), %ymm0, %ymm0 # sched: [6:1.00]
|
2017-07-11 00:36:03 +08:00
|
|
|
; BTVER2-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [3:2.00]
|
2017-04-24 06:08:17 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
2017-04-24 22:26:30 +08:00
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_xorps:
|
|
|
|
; ZNVER1: # BB#0:
|
2017-07-19 10:45:14 +08:00
|
|
|
; ZNVER1-NEXT: vxorps %ymm1, %ymm0, %ymm0 # sched: [1:0.25]
|
|
|
|
; ZNVER1-NEXT: vxorps (%rdi), %ymm0, %ymm0 # sched: [8:0.50]
|
|
|
|
; ZNVER1-NEXT: vaddps %ymm0, %ymm1, %ymm0 # sched: [3:1.00]
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-04-24 06:08:17 +08:00
|
|
|
%1 = bitcast <8 x float> %a0 to <4 x i64>
|
|
|
|
%2 = bitcast <8 x float> %a1 to <4 x i64>
|
|
|
|
%3 = xor <4 x i64> %1, %2
|
|
|
|
%4 = load <8 x float>, <8 x float> *%a2, align 32
|
|
|
|
%5 = bitcast <8 x float> %4 to <4 x i64>
|
|
|
|
%6 = xor <4 x i64> %3, %5
|
|
|
|
%7 = bitcast <4 x i64> %6 to <8 x float>
|
|
|
|
%8 = fadd <8 x float> %a1, %7
|
|
|
|
ret <8 x float> %8
|
|
|
|
}
|
|
|
|
|
2017-05-11 23:02:49 +08:00
|
|
|
define void @test_zeroall() {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_zeroall:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vzeroall
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-05-11 23:02:49 +08:00
|
|
|
; SANDY-LABEL: test_zeroall:
|
|
|
|
; SANDY: # BB#0:
|
2017-07-27 02:55:14 +08:00
|
|
|
; SANDY-NEXT: vzeroall
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-05-11 23:02:49 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_zeroall:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vzeroall # sched: [16:16.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-05-11 23:02:49 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_zeroall:
|
|
|
|
; SKYLAKE: # BB#0:
|
2017-09-19 14:19:27 +08:00
|
|
|
; SKYLAKE-NEXT: vzeroall # sched: [16:4.00]
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-05-11 23:02:49 +08:00
|
|
|
; BTVER2-LABEL: test_zeroall:
|
|
|
|
; BTVER2: # BB#0:
|
2017-07-27 21:12:08 +08:00
|
|
|
; BTVER2-NEXT: vzeroall # sched: [90:?]
|
2017-05-11 23:02:49 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_zeroall:
|
|
|
|
; ZNVER1: # BB#0:
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vzeroall # sched: [100:?]
|
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-05-11 23:02:49 +08:00
|
|
|
call void @llvm.x86.avx.vzeroall()
|
|
|
|
ret void
|
|
|
|
}
|
|
|
|
declare void @llvm.x86.avx.vzeroall() nounwind
|
|
|
|
|
|
|
|
define void @test_zeroupper() {
|
2017-08-01 23:14:35 +08:00
|
|
|
; GENERIC-LABEL: test_zeroupper:
|
|
|
|
; GENERIC: # BB#0:
|
|
|
|
; GENERIC-NEXT: vzeroupper
|
|
|
|
; GENERIC-NEXT: retq # sched: [1:1.00]
|
|
|
|
;
|
2017-05-11 23:02:49 +08:00
|
|
|
; SANDY-LABEL: test_zeroupper:
|
|
|
|
; SANDY: # BB#0:
|
2017-07-27 02:55:14 +08:00
|
|
|
; SANDY-NEXT: vzeroupper
|
This patch completely replaces the scheduling information for the SandyBridge architecture target by modifying the file X86SchedSandyBridge.td located under the X86 Target.
The SandyBridge architects have provided us with a more accurate information about each instruction latency, number of uOPs and used ports and I used it to replace the existing estimated SNB instructions scheduling and to add missing scheduling information.
Please note that the patch extensively affects the X86 MC instr scheduling for SNB.
Also note that this patch will be followed by additional patches for the remaining target architectures HSW, IVB, BDW, SKL and SKX.
The updated and extended information about each instruction includes the following details:
•static latency of the instruction
•number of uOps from which the instruction consists of
•all ports used by the instruction's' uOPs
For example, the following code dictates that instructions, ADC64mr, ADC8mr, SBB64mr, SBB8mr have a static latency of 9 cycles. Each of these instructions is decoded into 6 micro operations which use ports 4, ports 2 or 3 and port 0 and ports 0 or 1 or 5:
def SBWriteResGroup94 : SchedWriteRes<[SBPort4,SBPort23,SBPort0,SBPort015]> {
let Latency = 9;
let NumMicroOps = 6;
let ResourceCycles = [1,2,2,1];
}
def: InstRW<[SBWriteResGroup94], (instregex "ADC64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "ADC8mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB64mr")>;
def: InstRW<[SBWriteResGroup94], (instregex "SBB8mr")>;
Note that apart for the header, most of the X86SchedSandyBridge.td file was generated by a script.
Reviewers: zvi, chandlerc, RKSimon, m_zuckerman, craig.topper, igorb
Differential Revision: https://reviews.llvm.org/D35019#inline-304691
llvm-svn: 307529
2017-07-10 17:53:16 +08:00
|
|
|
; SANDY-NEXT: retq # sched: [1:1.00]
|
2017-05-11 23:02:49 +08:00
|
|
|
;
|
|
|
|
; HASWELL-LABEL: test_zeroupper:
|
|
|
|
; HASWELL: # BB#0:
|
2017-08-28 18:04:16 +08:00
|
|
|
; HASWELL-NEXT: vzeroupper # sched: [4:1.00]
|
|
|
|
; HASWELL-NEXT: retq # sched: [2:1.00]
|
2017-05-11 23:02:49 +08:00
|
|
|
;
|
2017-08-30 16:08:50 +08:00
|
|
|
; SKYLAKE-LABEL: test_zeroupper:
|
|
|
|
; SKYLAKE: # BB#0:
|
|
|
|
; SKYLAKE-NEXT: vzeroupper # sched: [4:1.00]
|
|
|
|
; SKYLAKE-NEXT: retq # sched: [2:1.00]
|
|
|
|
;
|
2017-05-11 23:02:49 +08:00
|
|
|
; BTVER2-LABEL: test_zeroupper:
|
|
|
|
; BTVER2: # BB#0:
|
2017-07-27 21:12:08 +08:00
|
|
|
; BTVER2-NEXT: vzeroupper # sched: [46:?]
|
2017-05-11 23:02:49 +08:00
|
|
|
; BTVER2-NEXT: retq # sched: [4:1.00]
|
|
|
|
;
|
|
|
|
; ZNVER1-LABEL: test_zeroupper:
|
|
|
|
; ZNVER1: # BB#0:
|
AMD family 17h (znver1) scheduler model update.
Summary:
This patch enables the following:
1) Regex based Instruction itineraries for integer instructions.
2) The instructions are grouped as per the nature of the instructions
(move, arithmetic, logic, Misc, Control Transfer).
3) FP instructions and their itineraries are added which includes values
for SSE4A, BMI, BMI2 and SHA instructions.
Patch by Ganesh Gopalasubramanian
Reviewers: RKSimon, craig.topper
Subscribers: vprasad, shivaram, ddibyend, andreadb, javed.absar, llvm-commits
Differential Revision: https://reviews.llvm.org/D36617
llvm-svn: 312237
2017-08-31 20:38:35 +08:00
|
|
|
; ZNVER1-NEXT: vzeroupper # sched: [100:?]
|
|
|
|
; ZNVER1-NEXT: retq # sched: [1:0.50]
|
2017-05-11 23:02:49 +08:00
|
|
|
call void @llvm.x86.avx.vzeroupper()
|
|
|
|
ret void
|
|
|
|
}
|
|
|
|
declare void @llvm.x86.avx.vzeroupper() nounwind
|
|
|
|
|
2017-04-24 06:08:17 +08:00
|
|
|
!0 = !{i32 1}
|