FazBrowse GitHub Viewer | Trending |
URL:
| Home
Tools: [Download Repo ZIP]   [Original HTTPS Page]

Ignore memory management object for native alloc funcitons by umar456 · Pull Request #3300 · arrayfire/arrayfire · GitHub

Ignore memory management object for native alloc funcitons - #3300

Open
umar456 wants to merge 3 commits into
arrayfire:masterfrom
umar456:native_mm_ignore_mm
Open

Ignore memory management object for native alloc funcitons#3300
umar456 wants to merge 3 commits into
arrayfire:masterfrom
umar456:native_mm_ignore_mm

Conversation

umar456 commented Sep 29, 2022

Copy link
Copy Markdown
Member

This PR adds a new memory manager example and fixes the native alloc function so that it ignores the af_memory_manager object.

Description

  • Creates a new memory manager example
  • The native alloc and native free functions now ignore the af_memory_manager object because they now allocate on the current device.
  • Empty allocations on the CPU backend do not call the alloc function

Changes to Users

N/A

Checklist

  • Rebased on latest master
  • Code compiles
  • Tests pass
  • Functions added to unified API
  • Functions documented

The native alloc and free functions are used to allocate and free
functions. These functions do not need the memory manager implementation
to work because they are just allocating directly with the underlying
backend. This change will now ignore the memory manager object
when allocating the memory.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
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.

2 participants


Back | FazBrowse Home | New Git URL