Add size validation for USM device/shared allocs

[RossBrunton]

The spec states that an allocation size higher than
DEVICE_INFO_MAX_MEM_ALLOC_SIZE should report an error. This has been
added to the cuda, hip and native cpu backends now.

The tests have also been updated, which sadly introduces a new
regression for level zero.

[kbenzie]

I don't think we can reliably have this check due to limitations in how the different adapters report max alloc size.

[RossBrunton]

I don't think we can reliably have this check due to limitations in how the different adapters report max alloc size.

What do you mean? The spec says that MAX_MEM_ALLOC_SIZE is the largest USM allocation that can be made.

[frasercrmck]

CUDA/HIP LGTM

[martygrant]

Unified Runtime -> intel/llvm Repo Move Notice

Information

The source code of Unified Runtime has been moved to intel/llvm under the unified-runtime top-level directory,
all future development will now be carried out there. This was done in intel/llvm#17043.

The code will be mirrored to oneapi-src/unified-runtime and the specification will continue to be hosted at oneapi-src.github.io/unified-runtime.

The contribution guide has been updated with new instructions for contributing to Unified Runtime.

PR Migration

All open PRs including this one will be labelled auto-close and shall be automatically closed after 30 days.
To allow for some breathing space, this automation will not be enabled until next week (27/02/2025).

Should you wish to continue with your PR you will need to migrate it to intel/llvm.
We have provided a script to help automate this process.

---

This is an automated comment.