trbauer

An alternate idea is to favor more C'ish syntax and list raw values with optional decoding as ::= ? ::= '[' ( | | ... others) ']' For example >>>>...

Yeah. A generative process would be great and extensible to other API intercept projects. But since our API set is just OpenCL we could use an embedded-DSL approach as well....

Here's a little more concrete idea on how to embed this. Here's an example API intercept with the adjustments. CL_API_ENTRY cl_int CL_API_CALL CLIRN(clGetPlatformInfo)( cl_platform_id platform, cl_platform_info param_name, size_t param_value_size, void*...

Just to follow up on this (NOTE: we decided against this "functional" approach for the moment, but I wanted to record the gist of the idea). My experiments demonstrated a...

A more conservative approach is to retain the _type driven_ features of the above and simply edit calls to `CALL_LOGGING_ENTER` and `CALL_LOGGING_EXIT`. The output syntax will then be determined uniformly...

I had similar goals. I wanted all the kernel argument binary values before enqueues (e.g. kernel arguments). This would include scalars and cl_mem object contents. We'd intercept in clSetKernelArg, and...