forked from mlcommons/ck
-
Notifications
You must be signed in to change notification settings - Fork 0
/
CONTRIBUTIONS.txt
315 lines (262 loc) · 6.36 KB
/
CONTRIBUTIONS.txt
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
CK uses standard 3-clause (new) BSD license. Contributions are welcome to
either improve existing functionality or add new functionality possibly using
new modules.
Contributors should clearly mark their contributions including date and remark.
You can easily contribute to CK and all related repositories by forking them
on GitHub and then submitting a pull request. Alternatively, you can submit
patches via [email protected] .
CK bugs can be reported here:
* https://github.com/ctuning/ck/issues
Bugs related to shared repositories (predictive analytics, reproducible
experimentation, autotuning, etc) should be reported via their corresponding
GitHub pages. For example, you can report bugs about progrma workflows
and autotuning here:
* https://github.com/ctuning/ck-autotuning/issues
Thank you for supporting this community project!
=================================================================================
Acknowledgments:
N: Grigori Fursin (alias: FGG)
H: http://fursin.net
O: cTuning foundation, France
C: original concept and design, real-world use cases, cKnowledge.org development
W: since Nov.1, 2014
N: Anton Lokhmotov
H: https://www.hipeac.net/~anton
O: dividiti, UK
C: real-world use cases
W: since Mar.1, 2015
N: Graham Markall
O: Continuum Analytics, UK
C: feedback on basic usage and help with Conda packaging (Anaconda scientific python distribution)
W:
N: Alexey Kravets
E:
H:
O: ARM, UK
C: discussing possible PENCIL autotuning scenarios via CK (within CARP project)
W:
N: Sven van Haastregt
E:
H:
O: ARM, UK
C: discussing possible PENCIL autotuning scenarios via CK (within CARP project)
W:
N: Vincent Grevendonk
E:
H:
O: ARM, UK
C: discussing possible PENCIL autotuning scenarios via CK (within CARP project)
W:
N: Abdul Wahid Memon
O:
C: checking how to convert GCC optimization flags to CK format for autotuning
W:
N: Valentin Dalibard
O: University of Cambridge, UK
C: feedback on autotuning and run-time adaptation
W:
N: Eiko Yoneki
O: University of Cambridge, UK
C: feedback on autotuning and run-time adaptation
W:
N: Cedric Nugteren
O: The Netherlands
C: testing CK on MacOS, validating OpenCL autotuning
W:
N: Sergey Yakushkin
E:
O: Synopsys
C: feedback, suggestions
W:
N: Lucas Nussbaum
E:
O: Universite de Lorraine, France
C: feedback on Debian packaging
W:
N: Andrei Lascu
O: Imperial College, UK
C: including clsmith to CK (OpenCL compiler testing)
W:
N: Alastair Donaldson
O: Imperial College, UK
C: including clsmith to CK (OpenCL compiler testing)
W:
N: Egor Pasko
E:
O: Google
C: feedback on basic usage
W:
N: Gianfranco Costamagna
E:
O:
C: feedback on Debian packaging
W:
N: Michael Kruse
O: ENS Paris, France
C: evaluating CK-based gemmbench (http://github.com/dividiti/gemmbench)
and providing feedback about autotuning and experiment reproducibility
W:
N: Chandan Reddy Gopal
E:
O: ENS Paris, France
C: evaluating CK for polyhedral autotuning (Pencil and PPCG from CARP project)
and providing various feedback
W:
N: Michel Steuwer
E:
O: University of Edinburgh, UK
C: feedback about documentation
W:
N: Ed Plowman
E:
O: ARM, UK
C: CK feedback and discussions
W:
N: Luigi Nardi
E:
O: STMicroelectronics, France
C: testing GCC crowdtuning engine and reporting a few minor bugs
W:
N: Michael Haidl
E:
H:
O:
C: helping test ARM64-based mobile phone to crowdsource optimizations
N: Toomas Remmelg
E:
H:
O: University of Edinburgh, UK
C: helping test ARM64-based Android mobile devices (flags and OpenCL)
N: Christophe Guillon
E:
O: STMicroelectronics, France
C: testing GCC crowdtuning engine and reporting a few minor bugs
W:
N: Leonid Fursin
E:
O:
C: feedback about crowdtuning on Samsung T-900 tablet
W:
N: Jiahao Chen
E:
O: MIT, USA
C: discussions about Julia language and CK-based performance autotuning
W:
N: Jarrett Revels
E:
O: MIT, USA
C: discussions about Julia performane tuning and feedback about CK-based LLVM crowdtuning on MacOS
W:
N: Aaron Smith
E:
O: Microsoft, USA
C: general discussions, feedback and help to move CK to Azure cloud (http://cknowledge.org)
W:
N: Dave Wilkinson
E:
O: University of Pittsburgh, USA
C: evaluating CK and providing several suggestions on usability
W:
N: Kenan Kalajdzic
E:
O:
C: reporting vulnerability in CK public repository (fixed)
W:
N: Yuriy Kashnikov
E:
O: Xored
C: crowd-tuning discussions
W:
N: Dmitry Savenko
E:
O: Xored
C: added continuous integration, various tests and fixed various problems with crowdtuning on MacOS
W:
N: Daniil Efremov
E:
O: Xored
C: testing and improving CK
W:
N: Michael Mcgeagh
E:
O: ARM, UK
C: reporting problem with yaml recording and CPU feature detection (in new format)
W:
N: Chris Cummins
E:
O: University of Edinburgh, UK
C: reporting problem with the 'ck status'
W:
N: Sam Ainsworth
E:
O: University of Cambridge, UK
C: reporting a few issues when converting his CGO 2017 artifacts to CK format (https://github.com/SamAinsworth/reproduce-cgo2017-paper)
W:
N: Nikolay Istomin
E:
O: Xored
C: fixed issue with widget fetching data from another source
W:
N: Todd Gamblin
E:
O: LLNL
C: discussing how to connect CK and spack, and fixing detection of native LLVM on MacOS (https://github.com/ctuning/ck-env/pull/70)
W:
N: Dave Greasley
E:
O: University of Bristol
C: fixed problem with repo UID when installing CK repo as zip:
* https://github.com/ctuning/ck/pull/92
* https://github.com/ctuning/ck/issues/91
provided feedback about RPi crowd-tuning: http://cKnowledge.org/rpi-crowd-tuning
W:
N: Stephen Herbein
E:
O: LLNL
C: customizing kernel to search soft in Spack directories
W: https://herbein.net
N: Flavio Vella
E:
O: Free University of Bozen-Bolzano
C: feedack and support
W:
N: Ivan Ospiov
E:
O: Xored
C: reported a problem with shared-repos.html; general feedback
W:
N: Leo Gordon
E:
O: dividiti
C: feedback, support and improvements
W:
N: Herve Guillou
E:
O: CodeReef
C: testing and feedback
W:
N: Vincent Rehm
E:
O: CodeReef
C: testing and feedback with LinuxBrew
W:
N: Thibaut Dumontet
E:
O: CodeReef
C: testing and feedback with LinuxBrew
W:
N: Alex Redshaw
E:
O: Arm
C: feedback about installation issue with Python 2.7
W: