1############################################################################## 2# OpenCL 2.0 submission details template 3# $Id $ 4# $URL $ 5############################################################################## 6# 7# This form should be filled in and included in the conformance submission 8# as the file submission_details.txt 9# 10# Lines beginning with "#" are comments to assist in filling out the template. 11# 12############################################################################## 13 14############################################################################## 15# 16# Submission information (mostly section 7 and F.5 of Conformance Process 17# Document) that needs to be copied onto the web submission form. 18# 19############################################################################## 20 21# Contact details. 22# 23Company: 24Contact Name: 25Contact Email: 26Contact Telephone: 27 28# Version of OpenCL specification being tested 29# 30OpenCL Version: 2.0 31 32# Statement of conformance listing each conformant product (at a specific 33# version) that is covered by this implementation. List each conformant product 34# on a separate line starting "Conformant Product:". The first in the list 35# is the product/device that the tests were actually run on. 36# 37# Each conformant product is likely to be one of: 38# * a type of computer (e.g. Windows XP PC) plus the software product 39# that contains this OpenCL implementation required to build and run 40# the tests, plus the OpenCL device tested, for example 41# * Conformant Product: Windows XP PC with Buzzleware OpenCL Library for Windows 0.2 42# with OpenCL running on a BrandX 322 PCIe GPU 43# 44Conformant Product: 45 46# CPU type and instruction set architecture level required by the implementation 47# and method of running the tests (for example X86_64 with SSE 4_2), and/or model 48# number 49# 50CPU Type: 51 52# OS with version number, including GUI framework if used by OpenKODE 53# implementation, e.g. Microsoft Windows XP SP2, Symbian 9.1 UIQ 3.1 54# 55OS Name and Version Number: 56 57# Tested compute device info, fill-in all the below fields for Compute Device, as returned by the clGetDeviceInfo query 58#ex: 59# Compute Device Type: CL_DEVICE_TYPE_GPU (show enum returned by CL_DEVICE_TYPE) 60# Compute Device Name: Brand X 322 PICe GPU, (as returned by CL_DEVICE_NAME) 61# Compute Device Version: OpenCL 2.0 MyGPU(TM) 1234, (as returned by CL_DEVICE_VERSION) 62# Compute Device Driver Version: OpenCL 2.0 build: 2.003.05.02 (as returned by CL_DRIVER_VERSION) 63# Compute Device OpenCL C Version: OpenCL 2.0 MyGPU(TM) 1234 (as returned by CL_DEVICE_OPENCL_C_VERSION) 64Compute Device Type: 65Compute Device Name: 66Compute Device Version: 67Compute Device Driver Version: 68Compute Device OpenCL C Version: 69 70# Platform information and version. These are the values returned from the 71# clGetPlaformInfo API call. 72Platform Profile: 73Platform Version: 74 75############################################################################## 76# 77# Further submission information (mostly section 7 of Conformance Process 78# Document). 79# 80############################################################################## 81 82# Date of tests used, 8 digit string as given in filename. 83# 84Tests date: 85 86 87# SHA-1 git identifier of the tests used from Gitlab (ex: 0a7770f98664a092c70d0a7d9a48d229b5fd8039) 88# 89Test ID: 90 91# Date of "Khronos Conformance Process" that this submission 92# adheres to (as shown in the change history at the start of the document). 93# 94Conformance Process Document date: 95 96# Date of "OpenCL Conformance Process Details" attachment to 97# the Khronos Conformance Process document that this submission adheres to 98# (as shown in the change history at the start of the attachment). 99# 100OpenCL Conformance Process Attachment date: 101 102# List of Khronos Bugzilla bugs filed for test bugs that have been fixed 103# by modifying the tests used in this submission. Separate bug numbers with 104# commas; if none, specify "none". It is OK to use an existing bug describing 105# the same problem. In any case, after filing this conformance submission, 106# add a comment to the bug referencing the submission tracking number 107# giving justification for the test change. 108# 109Test Bugs: 110 111############################################################################## 112# 113# Tested device configuration 114# 115############################################################################## 116 117# Max compute units (CL_DEVICE_MAX_COMPUTE_UNITS) 118CL_DEVICE_MAX_COMPUTE_UNITS: 119 120# Max clock frequency (CL_DEVICE_MAX_CLOCK_FREQUENCY) 121CL_DEVICE_MAX_CLOCK_FREQUENCY: 122 123# Max memory allocation size (CL_DEVICE_MAX_MEM_ALLOC_SIZE) 124CL_DEVICE_MAX_MEM_ALLOC_SIZE: 125 126# Image support (CL_DEVICE_IMAGE_SUPPORT), 1/0 127CL_DEVICE_IMAGE_SUPPORT: 128 129# Global memory size (CL_DEVICE_GLOBAL_MEM_SIZE) 130CL_DEVICE_GLOBAL_MEM_SIZE: 131 132# Max constant buffer size (CL_DEVICE_MAX_CONSTANT_BUFFER_SIZE) 133CL_DEVICE_MAX_CONSTANT_BUFFER_SIZE: 134 135# Local memory size (CL_DEVICE_LOCAL_MEM_SIZE) 136CL_DEVICE_LOCAL_MEM_SIZE: 137 138 139############################################################################## 140# 141# Extension Queries 142# 143############################################################################## 144# Show the list of supported extensions per device tested, each extension string on a separate line. 145 146