v1.5.0

[kris-rowe]

Features

Memory Pools

A device memory pool implementation is available in the occa::experimental namespace, targeting applications that frequently allocate/deallocate memory. See Example 17 for more details.

Provide feedback or share your use cases for this feature in the Experimental discussion category.

Outward Interoperability

An unwrap function has been added to the core classes—device, memory, stream, and streamTag—which returns a void* pointer to the mode-specific object used to implement each class.

This advance feature is intended to facilitate interoperability between occa and other accelerated libraries. Application developers are responsible casting the returned pointer to the correct mode-specific type.

In the future, a type-safe interface will be provided for the C++ API.

Breaking Changes

• Compiler flags set via occa::json kernel properties now take precedence over the corresponding environment variables. [Make compiler_flags setting take precedence over the compiler flag env var #622]

Bugfixes

• Dynamic @exclusive sizes [Dynamic @exclusive sizes #121]
• Build artifacts (e.g., binaries for kernel + launcher) are not durable [Build artifacts (e.g. binaries for kernel + launcher) are not dureable #515]
• Missing initial index value on @inner/@outer loops causes a segfault during translation. [Missing initial index value on @inner/@outer loops causes a segfault during translation. #610]
• A seg fault is encountered when destroying an occa::kernel that was created via a multi-kernel OKL file in CUDA, HIP, or DPC++ modes. [[CUDA][HIP][DPC++] Fix an issue with double frees when OKL has multip… #624]

Contributors

OCCA is a community driven project that relies on the support of people like you. Thank you everyone who contributed to this release!

• @MalachiTimothyPhillips
• @stgeke
• @SFrijters
• @noelchalmers
• @kris-rowe

Full Changelog: v1.4.0...v1.5.0

---

This discussion was created from the release v1.5.0.