1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
|
# --------------------------------------------------------------------------
#
# input.operations
# BLIS test suite
#
# This file contains input values that control which BLIS operations are
# tested as well as how those test runs are parameterized. We will now
# describe how each section or line type may be edited.
#
# ENABLING/DISABLING ENTIRE SECTIONS
# The values in the "Section overrides" section allow you to disable
# all operations in a given "level". Enabling a level here by itself
# does not enable every operation in that level; it simply means that
# the individual switches for each operation (in that level) determine
# whether or not the tests are executed. Use 1 to enable a section, or
# 0 to disable.
#
# ENABLING/DISABLING INDIVIDUAL OPERATION TESTS
# Given that an operation's section override switch is set to 1
# (enabled), whether or not that operation will get tested is
# determined by its local switch. For example, if the level-1v section
# override is set to 1, and there is a 1 on the line marked "addv",
# then the addv operation will be tested. Similarly, a 0 would cause
# addv to not be tested.
#
# ENABLING ONLY SELECT OPERATIONS
# If you would like to enable just a few (or even just one) operation
# without adjusting any section overrides (or individual operation
# switches), change the desired operation switch(es) to 2. This will
# cause any operation that is not set to 2 to be disabled, regardless
# of section override values. For example, setting the axpyv and gemv
# operation switches to 2 will cause the test suite to test ONLY axpyv
# and gemv, even if all other sections and operations are set to 1.
# NOTE: As long as there is at least on operation switch set to 2, no
# other operations will be tested. When you are done testing your
# select operations, you should revert the operation switch(es) back
# to 1.
#
# CHANGING PROBLEM SIZE/SHAPES TESTED
# The problem sizes tested by an operation are determined by the
# dimension specifiers on the line marked "dimensions: <spec_labels>".
# If, for example, <spec_labels> contains two dimension labels (e.g.
# "m n"), then the line should begin with two dimension specifiers.
# Dimension specifiers of -1 cause the corresponding dimension to be
# bound to the problem size, which is determined by values set in
# input.general. Positive values cause the corresponding dimension to
# be fixed to that value and held constant.
#
# Examples of dimension specifiers (where the dimensions are m and n):
#
# -1 -1 Dimensions m and n grow with problem size (resulting in
# square matrices).
# -1 150 Dimension m grows with problem size and n is fixed at
# 150.
# -1 -2 Dimension m grows with problem size and n grows
# proportional to half the problem size.
#
# CHANGING PARAMTER COMBINATIONS TESTED
# The parameter combinations tested by an operation are determined by
# the parameter specifier characters on the line marked "parameters:
# <param_labels>". If, for example, <param_labels> contains two
# parameter labels (e.g. "transa conjx"), then the line should contain
# two parameter specifier characters. The '?' specifier character
# serves as a wildcard--it causes all possible values of that parameter
# to be tested. A character such as 'n' or 't' causes only that value
# to be tested.
#
# Examples of parameter specifiers (where the parameters are transa
# and conjx):
#
# ?? All combinations of the transa and conjx parameters are
# tested: nn, nc, tn, tc, cn, cc, hn, hc.
# ?n conjx is fixed to "no conjugate" but transa is allowed
# to vary: nn, tn, cn, hn.
# hc Only the case where transa is "Hermitian-transpose" and
# conjx is "conjugate" is tested.
#
# Here is a full list of the parameter types used by the various BLIS
# operations along with their possible character encodings:
#
# side: l,r left, right
# uplo: l,u lower, upper
# trans: n,t,c,h no transpose, transpose, conjugate, Hermitian-
# transpose (i.e. conjugate-transpose)
# conj: n,c no conjugate, conjugate
# diag: n,u non-unit diagonal, unit diagonal
#
# --- Section overrides ----------------------------------------------------
1 # Utility
1 # Level-1v kernels
1 # Level-1m
1 # Level-1f kernels
1 # Level-2
1 # Level-3 micro-kernels
1 # Level-3
# --- Utility --------------------------------------------------------------
1 # randv
-1 # dimensions: m
1 # randm
-1 -1 # dimensions: m n
# --- Level-1v -------------------------------------------------------------
1 # addv
-1 # dimensions: m
? # parameters: conjx
1 # amaxv
-1 # dimensions: m
1 # axpbyv
-1 # dimensions: m
? # parameters: conjx
1 # axpyv
-1 # dimensions: m
? # parameters: conjx
1 # copyv
-1 # dimensions: m
? # parameters: conjx
1 # dotv
-1 # dimensions: m
?? # parameters: conjx conjy
1 # dotxv
-1 # dimensions: m
?? # parameters: conjx conjy
1 # normfv
-1 # dimensions: m
1 # invscalv
-1 # dimensions: m
? # parameters: conjalpha
1 # scalv
-1 # dimensions: m
? # parameters: conjalpha
1 # scal2v
-1 # dimensions: m
? # parameters: conjx
1 # setv
-1 # dimensions: m
1 # subv
-1 # dimensions: m
? # parameters: conjx
1 # xpbyv
-1 # dimensions: m
? # parameters: conjx
# --- Level-1m -------------------------------------------------------------
1 # addm
-1 -2 # dimensions: m n
? # parameters: transa
1 # axpym
-1 -1 # dimensions: m n
? # parameters: transa
1 # copym
-1 -2 # dimensions: m n
? # parameters: transa
1 # normfm
-1 -2 # dimensions: m n
1 # invscalm
-1 -2 # dimensions: m n
? # parameters: conjalpha
1 # scalm
-1 -2 # dimensions: m n
? # parameters: conjalpha
1 # scal2m
-1 -2 # dimensions: m n
? # parameters: transa
1 # setm
-1 -2 # dimensions: m n
1 # subm
-1 -2 # dimensions: m n
? # parameters: transa
1 # xpbym
-1 -1 # dimensions: m n
? # parameters: transa
# --- Level-1f kernels -----------------------------------------------------
1 # axpy2v
-1 # dimensions: m
?? # parameters: conjx conjy
1 # dotaxpyv
-1 # dimensions: m
??? # parameters: conjxt conjx conjy
1 # axpyf
-1 # dimensions: m
?? # parameters: conja conjx
1 # dotxf
-1 # dimensions: m
?? # parameters: conjat conjx
1 # dotxaxpyf
-1 # dimensions: m
???? # parameters: conjat conja conjw conjx
# --- Level-2 --------------------------------------------------------------
1 # gemv
-1 -2 # dimensions: m n
?? # parameters: transa conjx
1 # ger
-1 -2 # dimensions: m n
?? # parameters: conjx conjy
1 # hemv
-1 # dimensions: m
??? # parameters: uploa conja conjx
1 # her
-1 # dimensions: m
?? # parameters: uploc conjx
1 # her2
-1 # dimensions: m
??? # parameters: uploc conjx conjy
1 # symv
-1 # dimensions: m
??? # parameters: uploa conja conjx
1 # syr
-1 # dimensions: m
?? # parameters: uploc conjx
1 # syr2
-1 # dimensions: m
??? # parameters: uploc conjx conjy
1 # trmv
-1 # dimensions: m
??? # parameters: uploa transa diaga
1 # trsv
-1 # dimensions: m
??? # parameters: uploa transa diaga
# --- Level-3 micro-kernels ------------------------------------------------
1 # gemm
-1 # dimensions: k
1 # trsm
? # parameters: uploa
1 # gemmtrsm
-1 # dimensions: k
? # parameters: uploa
# --- Level-3 --------------------------------------------------------------
1 # gemm
-1 -1 -1 # dimensions: m n k
nn # parameters: transa transb
1 # gemmt
-1 -1 # dimensions: m k
?nn # parameters: uploc transa transb
1 # hemm
-1 -1 # dimensions: m n
??nn # parameters: side uploa conja transb
1 # herk
-1 -1 # dimensions: m k
?n # parameters: uploc transa
1 # her2k
-1 -1 # dimensions: m k
?nn # parameters: uploc transa transb
1 # symm
-1 -1 # dimensions: m n
??nn # parameters: side uploa conja transb
1 # syrk
-1 -1 # dimensions: m k
?n # parameters: uploc transa
1 # syr2k
-1 -1 # dimensions: m k
?nn # parameters: uploc transa transb
1 # trmm
-1 -1 # dimensions: m n
??n? # parameters: side uploa transa diaga
0 # trmm3
-1 -1 # dimensions: m n
??n?n # parameters: side uploa transa diaga transb
1 # trsm
-1 -1 # dimensions: m n
??n? # parameters: side uploa transa diaga
|
