aboutsummaryrefslogtreecommitdiff
path: root/gas.py
diff options
context:
space:
mode:
authorAdrian Kummerlaender2020-03-26 21:30:05 +0100
committerAdrian Kummerlaender2020-03-26 21:30:05 +0100
commit18c27ca60bc364d5e6cb811f56ec8c4f72867ac9 (patch)
tree1ad7ba010272b9d04c822e33a00a28d48be19274 /gas.py
parent2af16451f5119398c34ef9bd8626791e0498b9ab (diff)
downloadboltzgas-18c27ca60bc364d5e6cb811f56ec8c4f72867ac9.tar
boltzgas-18c27ca60bc364d5e6cb811f56ec8c4f72867ac9.tar.gz
boltzgas-18c27ca60bc364d5e6cb811f56ec8c4f72867ac9.tar.bz2
boltzgas-18c27ca60bc364d5e6cb811f56ec8c4f72867ac9.tar.lz
boltzgas-18c27ca60bc364d5e6cb811f56ec8c4f72867ac9.tar.xz
boltzgas-18c27ca60bc364d5e6cb811f56ec8c4f72867ac9.tar.zst
boltzgas-18c27ca60bc364d5e6cb811f56ec8c4f72867ac9.zip
Prototype port to 3D
What is it with OpenCL @ GPU and arrays of 3-dimensional vectors?! Luckily I vaguely remembered encountering this problem before when implementing my OpenCL LBM code but why on earth is the compiler not warning about this? I guess the underlying reason has to do with the data alignment requirements on the GPU but still...
Diffstat (limited to 'gas.py')
0 files changed, 0 insertions, 0 deletions