Andreas Klöckner

To my mind, this is a mailing list/tech support issue more than a bug in PyOpenCL. i'd suggest you use [code like this](https://github.com/inducer/loopy/blob/fe33aaf12b209a528351a1b4415ec9d687a8657a/loopy/tools.py#L231-L279) to align your numpy arrays to start...

Thanks for explaining, I remember now. The current `Array.events` system needs to be redone to wait on reads before making in-place changes. [!91](https://gitlab.tiker.net/inducer/pyopencl/merge_requests/91) adds synchronization for WAR in `.get()`, but...

@zachjweiner Could you remind me which way this issue went? According to my experiments, I believe `2*x` does not *currently* add the resulting event to `x.events` (as of a60b4ed), so...

> * We could mark `pyopencl.tools.Argument` with a flag and have any new code pass those in `__init__(arguments)`? Something like how `ArrayArg` seems to work in `loopy`. Not sure what...

For now, pyopencl unconcditionally provides access to the include files that come "in the box", whether they're used or not. I'm not sure how I feel about compilers complaining about...

I think I simply must have not realized that it was necessary to consider that case when I wrote the struct alignment code. I'd be grateful for a PR.

To cut down on noise in my email, I'm unsubscribing from this PR. When it next needs my attention, please @-mention me or hit the "request review" button. Otherwise, I...

I feel like you might be misunderstanding something here... "binary" operator refers to "having two operands", i.e. "a+b". A unary operator is one with one operand, e.g. "-a".

Gitlab sister MR for CI: https://gitlab.tiker.net/inducer/pycuda/-/merge_requests/47

In general, make new issues for separate topics. (Spoiler alert: object arrays aren't happening. They're tied to the Python runtime, which doesn't exist on the GPU. Enums are more likely,...