Skip to content

Use std atomic in Metal GPU accelerator map - #37

Open
gripeyes wants to merge 1 commit into
OpenMoonRay:mainfrom
gripeyes:fix/metal-gpu-accelerator-atomic
Open

Use std atomic in Metal GPU accelerator map#37
gripeyes wants to merge 1 commit into
OpenMoonRay:mainfrom
gripeyes:fix/metal-gpu-accelerator-atomic

Conversation

@gripeyes

Copy link
Copy Markdown

Compatibility:

build

Issues/Tickets:

Release notes comment:

Updated the Metal GPU accelerator map to use the standard C++ atomic implementation.

Comments for the reviewer:

This is the isolated MetalGPUAccelerator change extracted from the historical OpenMoonRay platform-alignment work.

The map value type now uses std::atomic<MetalGPUPrimitiveGroup*> instead of tbb::atomic<MetalGPUPrimitiveGroup*>, providing compatibility with newer oneTBB versions where the legacy TBB atomic type is no longer available.

The required <atomic> header is included explicitly.

No other Metal, GPU, rendering, dependency, or submodule changes are included.

Look or scene setup change:

No expected look or scene setup changes.

Special notes for production:

This is a build-compatibility change for the Metal GPU accelerator and newer oneTBB versions.

Attention/Reviewers:

AI Assisted Development:

Assisted-by: OpenAI Codex / GPT-5.6

Checklist:

  • Documentation has been updated.
  • Includes new unit tests.
  • Includes new RATS tests.

No documentation, unit-test, or RATS changes are included for this isolated type replacement.

Signed-off-by: Jakub Svoboda <132791205+rolledhand@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant