Changes between Initial Version and Version 1 of Ticket #43710, comment 4
- Timestamp:
- May 15, 2014, 2:59:29 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #43710, comment 4
initial v1 1 *The OpenGL errors are normal on OSX and those are not fatal. As the message says, the compilation fails but it will use a fallback method. (which in what's currently used shouldn't make much of a difference visually).1 The OpenGL errors are normal on OSX and those are not fatal. As the message says, the compilation fails but it will use a fallback method. (which in what's currently used shouldn't make much of a difference visually). 2 2 3 This error happens because I rely on the GLSL 1.5 compatibility profile for those shaders . I basically want to use some of the advanced GLSL features not available in previous versions, but I don't want to give up the legacy pipeline. To go to full 3.x core profile, I'd need to completely give up immediate mode, use my own vertex shaders, re-implement the matrix stuff myself, etc, etc ... which I'm really not willing to do so I can just draw a few lines and 2 textured quads with pixel shaders applied ...3 This error happens because I rely on the GLSL 1.5 compatibility profile for those shaders and OSX doesn't have any of the compatibility profiles. I basically want to use some of the advanced GLSL features not available in previous versions, but I don't want to give up the legacy pipeline. To go to full 3.x core profile, I'd need to completely give up immediate mode, use my own vertex shaders, re-implement the matrix stuff myself, etc, etc ... which I'm really not willing to do so I can just draw a few lines and 2 textured quads with pixel shaders applied ... 4 4 5 5 6 * The CL error is the real issue. It says it selected "Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz" which is a CPU implemention of OpenCL since your GPU doesn't do OpenCL. Now, that means it evaluated the device and thought that it was capable of running fosphor. But obviously it wasn't because even though the initialization went nicely, when it tried to actually queue the execution of some compuation, it failed with CL_INVALID_WORK_GROUP_SIZE. To know if this is justified, it would be useful to see the actual capabilities of the device. I attached a clInfo.c test program that should print all the required info. If you could compile and execute it and post the results, it would be nice. 6 7 The CL error is the real issue. It says it selected "Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz" which is a CPU implemention of OpenCL since your GPU doesn't do OpenCL. Now, that means it evaluated the device and thought that it was capable of running fosphor. But obviously it wasn't because even though the initialization went nicely, when it tried to actually queue the execution of some compuation, it failed with CL_INVALID_WORK_GROUP_SIZE. To know if this is justified, it would be useful to see the actual capabilities of the device. I attached a clInfo.c test program that should print all the required info. If you could compile and execute it and post the results, it would be nice. 7 8 8 9 PS: Also, btw, I now _hate_ trac ... the damn 'attach file' function doensn't warn you it will just drop the whole comment you already typed ...