Richard Membarth

For the moment, we decided for option 2, but in the long run we would like to track the wrap-around property in the type.

Is the behaviour exactly identical to `pe_info()`, expect for the fact that it should make compilation fail?

The hash was on the wrong branch, I've updated my previous post.

Same problem here: https://github.com/AnyDSL/imbatracer/commits/forever

So this needs to be resolved earlier?

Not really urgent. Pops up once in a while for more complex code (which gets then not optimized). Is there a timeline for CoC integration?

This is actually not a bug ... we expect pointers on the GPU to reside in the global address space, e.g. `&[1][i8]`. In case you modify your example to use...

The setup script will setup everything you need to get started. From there you create your own application using the built components (llvm, thorin, impala | artic, runtime). For jit,...

We should go for: ```cmake set(foo bar) ``` We have this for all repos apart from Impala and Thorin for historical reasons. DFKI cloud is also available from outside, but...

What's actually the purpose of those CMake files? They are nowhere used?