[SYCL] Optimize checkValueRange

[Pennycook]

checkValueRange is used to determine if an nd_range is compatible with -fsycl-queries-fit-in-int, and is run as part of every kernel launch.

The previous implementation checked the size of each component of the global range, local range, offset, and global range + offset, and also checked the linearized version of each of these values.

The new implementation simplifies these checks, based on the following logic:

• The linear global range size must be >= every component of the global range.
  If the linear global range fits in int, we don't need to check anything else.

• Each value in the global range must be >= the value in the local range.
  If the global range fits in int, we don't need to check the local range.

• There is no need to check offset-related values if the offset is zero.

The new implementation also makes use of __builtin_mul_overflow where available. This shifts the burden of maintaining fast code for these checks to the compiler, and allows us to benefit from aggressive optimizations.

The new implementation could be optimized further if there was a quick way to check whether an nd_range has an offset.

[Pennycook]

A note to reviewers: I had to remove a test, but the test was invalid. In SYCL, the global range must be divisible by the local range, and it makes no sense to enqueue a global range of {1, 1} with a local range that is outside the range of an int.

With my proposed changes, the test as written still throws an exception, it's just a different exception. Depending on the device, it will fail either because: the local range is too large for the device (e.g., PVC is limited to {1024, 1024, 1024}); or because the global range isn't divisible by the local range.

[Pennycook]

The failing test looks unrelated to me.

[uditagarwal97]

LGTM. Minor NITs