浅谈opencl之错误码
opencl采用了统一的错误码,各个API通用
Error | Description |
CL_SUCCESS | Command executed successfully without error. |
CL_DEVICE_NOT_FOUND | No OpenCL devices found matching criteria. |
CL_DEVICE_NOT_AVAILABLE | OpenCL device is not currently available |
CL_COMPILER_NOT_AVAILABLE | Program created with source, but no OpenCL C compiler is available. |
CL_MEM_OBJECT_ALLOCATION_FAILURE | Failure to allocate memory for a memory or image object. |
CL_OUT_OF_RESOURCES | Insufficient resources to execute command. |
CL_OUT_OF_HOST_MEMORY | Insufficient memory available on the host to execute command. |
CL_PROFILING_INFO_NOT_AVAILABLE | Profiling information is not available for the event or the command-queue does not have profiling enabled. |
CL_MEM_COPY_OVERLAP | Two buffers overlap the same region of memory. |
CL_IMAGE_FORMAT_MISMATCH | Images do not share the same image format. |
CL_IMAGE_FORMAT_NOT_SUPPORTED | Specified image format is not supported |
CL_BUILD_PROGRAM_FAILURE | Unable to build executable for program. |
CL_MAP_FAILURE | Memory region could not be mapped into host memory. |
CL_INVALID_VALUE | An invalid value was specified for one or more arguments to the command. |
CL_INVALID_DEVICE_TYPE | The passed-in device type is not a valid value. |
CL_INVALID_PLATFORM | The passed-in platform is not a valid value |
CL_INVALID_DEVICE | The passed-in device is not a valid value |
CL_INVALID_CONTEXT | The passed-in context is not a valid value |
CL_INVALID_QUEUE_PROPERTIES | The device does not support command-queue properties. |
CL_INVALID_COMMAND_QUEUE | The passed-in command-queue is not a valid value. |
CL_INVALID_HOST_PTR | The host pointer is not valid |
CL_INVALID_MEM_OBJECT | The passed-in memory object is not a valid value. |
CL_INVALID_IMAGE_FORMAT_DESCRIPTOR | The passed-in image format descriptor is not valid. |
CL_INVALID_IMAGE_SIZE | The device does not support the image dimensions. |
CL_INVALID_SAMPLER | The passed-in sampler is not a valid value. |
CL_INVALID_BINARY | An invalid program binary was passed in. |
CL_INVALID_BUILD_OPTIONS | One or more build options are not valid. |
CL_INVALID_PROGRAM | The passed-in program is not a valid value. |
CL_INVALID_PROGRAM_EXECUTABLE | The program was not successfully built into an executable for the devices associated with the command-queue |
CL_INVALID_KERNEL_NAME | The named kernel does not exist in the program. |
CL_INVALID_KERNEL_DEFINITION | The kernel defined in the program source is not valid. |
CL_INVALID_KERNEL | The passed-in kernel is not a valid value |
CL_INVALID_ARG_INDEX | The argument referred to by the argument index is not valid for the kernel |
CL_INVALID_ARG_VALUE | The kernel argument value is NULL for a nonlocal argument or non-NULL for a local argument. |
CL_INVALID_ARG_SIZE | The argument size does not match the kernel argument. |
CL_INVALID_KERNEL_ARGS | One or more kernel arguments have not been assigned values. |
CL_INVALID_WORK_DIMENSION | The value of the work dimension is not a value between 1 and 3. |
CL_INVALID_WORK_GROUP_SIZE | The local or global work size is not valid |
CL_INVALID_WORK_ITEM_SIZE | One or more work-item sizes exceed the maximum size supported by the device. |
CL_INVALID_GLOBAL_OFFSET | The global offset exceeds supported bounds. |
CL_INVALID_EVENT_WAIT_LIST | The wait list provided is either an invalid size or contains nonevents in it. |
CL_INVALID_EVENT | The passed-in event is not a valid value |
CL_INVALID_OPERATION | Executing the command caused an invalid operation to occur. |
CL_INVALID_GL_OBJECT | There was a problem with the OpenGL-referenced object |
CL_INVALID_BUFFER_SIZE | The buffer size specified was out of bounds. |
CL_INVALID_MIP_LEVEL | The mipmap level specified for an OpenGL texture is not valid for the OpenGL object. |
CL_INVALID_GLOBAL_WORK_SIZE | The global work size passed in is not valid because it is either 0 or exceeds the dimen-sions supported by the device |
浅谈opencl之错误码相关推荐
- 浅谈OpenCL之Platform API(2)
OpenCL Contexts context是贯串 opencl 程序的核心,也是host 与device 交互的唯一通道,是内存申请维护,命令队列的创建等功能的基础. 不同的plaform,可以申 ...
- 浅谈OpenCL之 应用程序总体步骤思路
一般Opencl 应用程序步骤,为了保证原英文意思 没有翻译中文: 1:Query which platforms are present. 2: Query the set of devices ...
- 浅谈OpenCL之Platform API(1)
Platform API 为opencl 初始化首先要使用的API,主要是获取到platform 以及device. OpenCL Platforms opencl 应用程序第一步首先就是要查询ope ...
- 浅谈opencl之整体框架
结合四大模型,以CPU和GPU平台为例子,opencl整体框架如下: CPU为host端, GPU为device端, host和device端的交互是以context为主.context贯穿到整个op ...
- 浅谈OpenCL之API分类
OpenCL为应用开发提供了丰富的API,按照其四大模型其API主要分为以下三类: Platform API 平台API主要是由HOST调用,可以用来查询opencl plaftform, devic ...
- 浅谈Opencl四大模型之Programming Model
Opencl 平台模型解决了 硬件兼容问题,将各种硬件抽象成了模型:执行模型解决了opencl程序如何运行的问题:内存模型解决了opencl 内存管理 问题,而编程模型(programming mod ...
- 浅谈Opencl四大模型之Memory Model
运行模型(execution model)讲述了一个kernel怎么样在opencl平台运行,host喝kernel如何交互的,kernel代码如何编译的等等,但是没有涉及到opencl内存的管理方式 ...
- 浅谈OpenCL四大模型之Execution Model
OpenCL执行模型(Execution Model)解释了opencl程序是如何运行的,是理解opencl的基础. OpenCL程序 Opencl应用程序一般分为host部分和kernel部分组成, ...
- 浅谈Opencl四大模型之Platform model
Opencl是一种典型的异构架构,可以很好的实施并发性,为了简化并行计算复杂度以及兼容各个芯片差异性,opencl将其抽象为四大模型(Platform model, Execution model,M ...
最新文章
- 为什么阿里强制 boolean 类型变量不能使用 is 开头?
- mysql select 返回列,是否可以对在mysql SELECT语句中返回列的顺序进行排序?
- mysql 查看导出数据字典
- Android从无知到有知——NO.7
- laravel CURD
- Linux SSH使用公钥私钥实现免登陆 以及 登陆失败、公钥失效的处理转
- Python中lambda的用法及其与def的区别解析
- 一些常见的代码异味及解决之道
- eclipse提交代码至GitHub
- 达内java考试_达内第一次JAVA考试题
- 线性代数 --- 矩阵与向量的乘法
- 内存核心频率、工作频率,等效频率、总线频率
- 无线鼠标计算机不识别,教你笔记本电脑检测不到无线鼠标如何解决
- XDOJ1184 - 贪心的小白羊
- matlab数字信号处理(1)——正弦信号生成与时域分析
- 2023年华中科技大学新闻传播专硕考研上岸前辈备考经验指导
- 状态压缩Dp模板-玉米田
- 【原创】解决JT2Go二次开发提示license key无效问题
- Unity3D屏幕划线附带物理碰撞效果
- 学人工智能数学要好吗?