Latest revision |
Your text |
Line 1: |
Line 1: |
− | = Project Report = | + | = Development Logs = |
| | | |
| == Project Plan == | | == Project Plan == |
Line 54: |
Line 54: |
| | | |
| == To Do List == | | == To Do List == |
− |
| |
− | * '''Memory Allocation''' : One of the major challenges I faced was finding the OpenCL counterpart of bu_malloc which works fine while passing the variables from .c to .cl file. While I tried with malloc as is used normally in C programs, it apparently didn't work. The renderings were simply not occurring in the OpenCL version. Hence, the HYP and SUPERELL primitives, which didn't use the bu_malloc command, rendered easily while others didn't. The patches submitted above have no compilation or computation error. If the memory allocation thing works, they'd render just as fine.
| |
− |
| |
− | * '''Using Printf statement''': Another issue where I got stuck was being unable to use printf statement in OpenCL files. The strategy to debug opencl kernels using printf is to enable printf command by passing enumerations stated below in an array of context properties to the function, clCreateContext, which creates opencl context as follows:
| |
− | <pre>
| |
− | CL_PRINTF_CALLBACK_ARM 0x40B0
| |
− | CL_PRINTF_BUFFERSIZE_ARM 0x40B1
| |
− | cl_context_properties context_properties[] =
| |
− | {
| |
− | CL_PRINTF_CALLBACK_ARM, (cl_context_properties)printf_callback,
| |
− | CL_PRINTF_BUFFERSIZE_ARM, (cl_context_properties)0x100000,
| |
− | CL_CONTEXT_PLATFORM, (cl_context_properties)platform,
| |
− | 0
| |
− | };
| |
− | </pre>
| |
− | This enables the device side printf built in function for OpenCL C versions prior to 1.2. It also extends the cl_context_properties enumeration to allow a user defined printf callback and/or printf buffer size. OpenCL kernel code then has access to:
| |
− | #pragma OPENCL EXTENSION cl_arm_printf : enable
| |
− | This pragma must be enabled for a kernel to have access to the printf built in function in OpenCL C versions prior to 1.2.
| |
− |
| |
− | For the purpose of debugging in mged I used bu_log instead of printf by passing following array of context properties
| |
− | <pre>
| |
− | cl_context_properties context_properties[] =
| |
− | {
| |
− | CL_PRINTF_CALLBACK_ARM, (cl_context_properties)bu_log,
| |
− | CL_PRINTF_BUFFERSIZE_ARM, (cl_context_properties)0x100000,
| |
− | CL_CONTEXT_PLATFORM, (cl_context_properties)platform,
| |
− | 0
| |
− | };
| |
− | </pre>
| |
− |
| |
− | But unfortunately this doesn't work and reports error that context cannot be created. This needs further investigation. The print statement would also be useful for debugging the memory allocation issue, as to where and why it is failing.
| |
− |
| |
− | == References ==
| |
− | * '''Project Plan''': https://brlcad.org/wiki/User:Rishabhsuthar32/GSoC20/Project
| |
− | * '''Development Logs''': https://brlcad.org/wiki/User:Rishabhsuthar32/GSoC20/Log
| |