Might be related to #520

What is wrong?

When an array constant is defined, the kernel function messes up the variables, apparently the input variables itself is overwritten by the constant array.

Where does it happen?

After running a GPU.js kernel and observing the output.

How do we replicate the issue?

Use this code:

const { GPU } = require('gpu.js');
const gpu = new GPU();
const naiveFn = gpu.createKernel(function(a, b) {
    return a[this.thread.y][this.thread.x];
    // return b[this.thread.y][this.thread.x];
}, {
  constants: {
    // zzz: [21,23],
  }
}).setOutput([2, 2]);

const c = naiveFn([[2,3], [5,7]], [[11,13],[17,19]]);
console.log(c);

A very simple function that just returns the input array.

When this is executed, the result is normal, i.e.:

[ Float32Array [ 2, 3 ], Float32Array [ 5, 7 ] ] when return a line is active, and
[ Float32Array [ 11, 13 ], Float32Array [ 17, 19 ] ] when return b line is active.

However, if I uncomment the constants property in settings object, which defines an array zzz, the output becomes:

[ Float32Array [ 21, 23 ], Float32Array [ 0, 0 ] ] when return a line is active, and
[ Float32Array [ 2, 3 ], Float32Array [ 5, 7 ] ] when return b line is active.

As you can see, b in the kernel now holds the first input array, and a in kernel becomes the array defined in constants.zzz.

How important is this (1-5)?

5

Expected behavior (i.e. solution)

The array constant definition should not affect the parameters, and the correct result (i.e. the first one) should be returned regardless.

Other Comments