In a nutshell, after adding a CodeXL breakpoint at clEnqueueNDRangeKernel and starting debug, I would get a new tab with “ No Source Available. I can now debug c#/.net openCL applications using CodeXL… this rocks! After some playing around it finally worked!!! The manual breakpoint and F11 you had me try fixed it. Once you're done verifying, you can remove those three breakpoints, and proceed to add clEnqueueNDRangeKernel as a breakpoint as explained in this post. If the same breakpoint is hit again, the workaround was not needed and you can use CodeXL without it.ĥ. If none of the breakpoints are hit, the workaround was necessary, restore it (until you no longer need to use CodeXL). Debug with CodeXL and the three breakpoints again. Now try undoing the workaround as I described in my original post.Ĥ. One of the breakpoints, most likely clGetPlatformIDs, will be hit.ģ. In CodeXL's breakpoints dialog, set breakpoints on "clGetPlatformIDs", "clCreateContext" and "clCreateContextFromType"Ģ. I may have misread your original post, and the workaround I described might not be necessary, please try the following:ġ. The same is true for clEnqueueTask, if you happen to use that API. This will also take you to the aforementioned temporary kernel source file. Once you get there, simply press "Step in" (F11) to go into kernel debugging. To debug an OpenCL kernel, you can also set an API breakpoint on clEnqueueNDRangeKernel (via CodeXL's "New CodeXL breakpoint." dialog) - this should show the API call in your code if you debug with CodeXL. When an CodeXL thinks the application "generates" OpenCL source code, it will create a temporary cl source file and use that as the source for the kernel, showing it if you try to debug it.ĬodeXL also has API-level debugging - it allows you to set breakpoint at OpenCL API functions, such as clCreateProgramWithSource or clEnqueueNDRangeKernel. However, if the cl source does not match any of those files (or there are no such files), CodeXL still logs the creation of the program - some applications have OpenCL kernels embedded in the source as string constants, or even generate OpenCL code on-the-fly, and CodeXL supports those as well: Multi-GPU frame pacing in Battlefield 3 and Battlefield 4 is now enabled for non-XDMA configurations running resolutions >1600p.When an OpenCL program is created via clCreateProgramWithSource, CodeXL should intercept that function call and compare the source string against available *.cl files (available = part of the project in Visual Studio, or present in the "Kernel sources" folder in standalone CodeXL). Hangs and stuttering resolved for the Mantle codepath in Battlefield 4 users are now encouraged to try mGPU.This is a great example of rendering technology supporting an integral element of the game! A notable percentage of the game’s rendering budget has been spent on the novel shadowing algorithms.Īs a reminder, THIEF will be patched to support Mantle and AMD TrueAudio technologies in early March. Complex shadowing systems to support THIEF’s dependence on shadows as a core gameplay mechanic.Silhouette-enhancing tessellation to improve character geometry.Compute shader-accelerated depth of field for realistic focal lengths.In addition, everyone will benefit from the Square/AMD collaboration through a host of graphical effects: At launch, AMD Radeon customers will have day-one support for: 4K gaming, AMD Eyefinity technology, AMD CrossFire technology and advantageous DirectX 11 performance. Throughout development of the PC and console versions of the game, this exciting reimagining of a classic franchise was built with AMD Radeon products in mind. THIEF is an exclusive partner of the AMD Gaming Evolved program. We have a discussion thread open on this driver right here.ĪMD is pleased to announce the AMD Catalyst 14.2 Beta release to coincide with the North American launch of THIEF! THIEF is an important title for the AMD Gaming Evolved program, rife with technologies optimized specifically for AMD Radeon™ graphics architectures-plus it’s just a plain ol’ fun game to play, with a franchise people know and love. This driver works with Windows 7, 8 and 8.1. Download the AMD Catalyst 14.2 Beta V1.3 driver.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |