[GPU Logic Bug] SELECT DISTINCT <column> FROM <table> Brings Errors

[qwebug]

Describe:

SELECT DISTINCT <column> FROM <table> brings different results, when using CPU-only configurations and GPU-used configurations.

SQL with CPU-only Config:

CREATE TABLE t1(c0 integer , SHARD KEY(c0)) WITH (shard_count=28);
INSERT INTO t1(c0) VALUES(1);
INSERT INTO t1(c0) VALUES(2);
ALTER SESSION SET EXECUTOR_DEVICE='CPU';
SELECT DISTINCT - (t1.c0) FROM t1;

Result:

EXPR$0
-2
-1

SQL with GPU-used Config:

ALTER SESSION SET EXECUTOR_DEVICE='GPU';
SELECT DISTINCT - (t1.c0) FROM t1;

Result:

EXPR$0
-1
-2

Environment:

Docker Deployment

https://hub.docker.com/layers/heavyai/heavyai-ee-cuda/latest/images/sha256-5af3ad3a00cbc5ce09c299b8b81cda96521a27373dbb1e59209c02358cfd9b1f?context=explore

Docker DIGEST: sha256:5af3ad3a00cbc5ce09c299b8b81cda96521a27373dbb1e59209c02358cfd9b1f

HeavyDB Version: 7.1.0-20230821-eae9ec17da

HeavyDB license: Free Edition

[qwebug]

This problem came up at HeavyDB Version: 7.1.0-20230821-eae9ec17da (Docker: https://hub.docker.com/layers/heavyai/heavyai-ee-cuda/v7.1.0/images/sha256-5af3ad3a00cbc5ce09c299b8b81cda96521a27373dbb1e59209c02358cfd9b1f?context=explore ) .
And it has been fixed at HeavyDB Version: 8.0.2 (Docker: https://hub.docker.com/layers/heavyai/heavyai-ee-cuda/v8.0.2/images/sha256-e343a97e342db3ba4e0ca069d567b76826dc7f6f95d07ee2af611f218194d28b?context=explore), after my verification.
Thanks to the developers for their contributions.