Andreas Klöckner
Andreas Klöckner
Instead of hardcoding a `bool` return type to the (previously general) `_make_binary_op`, add an optional `force_return_dtype=None` argument.
I don't really like the idea. Forcibly preprocessing source introduces a potentially large performance hit, and adding an option introduces a rarely used codepath that will invariably pick up bugs....
Is this what you have in mind? https://github.com/inducer/aksetup/pull/1
You can call `clCreateProgramWithBinary` without a problem, see [here](https://github.com/inducer/pyopencl/blob/d0d0addccd5d71a32a425d274663373909ff5254/test/test_wrapper.py#L645). As for more direct support for offline compilers, since I don't have a device that uses one, I would have to...
Could you add/update the docs?
That academia.edu link doesn't seem to work.
What is that latest version?
`six.moves.intern` should be in six 1.9.0: https://bitbucket.org/gutworth/six/src/a9b120c9c49734c1bd7a95e7f371fd3bf308f107/six.py?at=1.9.0#cl-235
For posterity, the resulting kernel is this: ``` for D_dim_0, D_dim_1, j_outer ↱ D_fetch[D_dim_0, D_dim_1] = D[D_dim_0, D_dim_1 + 5*j_outer] {id=D_fetch_rule} │ end D_dim_0, D_dim_1, j_outer │ for i, e...
This seems simple to implement, but it's unlikely I'll have the spare bandwidth for it soon. I'm happy to look at PRs though.