← 返回首页
Make the symbolManager a static pointer to avoid destruction on exit by umar456 · Pull Request #2769 · arrayfire/arrayfire · GitHub
Skip to content

Navigation Menu

Toggle navigation
Sign in
Appearance settings
Search or jump to...

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Appearance settings
Resetting focus

Make the symbolManager a static pointer to avoid destruction on exit#2769

Merged
umar456 merged 2 commits into
arrayfire:masterfrom
umar456:unified_static
Feb 19, 2020
Merged

Make the symbolManager a static pointer to avoid destruction on exit#2769
umar456 merged 2 commits into
arrayfire:masterfrom
umar456:unified_static

Conversation

Copy link
Copy Markdown
Member

umar456 commented Feb 17, 2020

  • Avoid releasing symbol manager. Let OS release resources
  • Does not affect leak sanitizer
  • Use static instead of thread local to avoid loading the library
    multiple times

umar456 force-pushed the unified_static branch 2 times, most recently from 4cd6714 to a09959c Compare February 18, 2020 00:57
* Avoid releasing symbol manager. Let OS release resources * Does not affect leak sanitizer * Use static instead of thread local to avoid loading the library multiple times * Move activeBackend and activeHandle out of symbol manager since AFSymbolManager is a singleton class now. It didn't make sense to have those variables in there anyway because they do not do anything with the symbols. Added multi-threaded tests to make sure expected behavior when switching backends
Comment thread test/backend.cpp Show resolved Hide resolved
umar456 merged commit 70a8051 into arrayfire:master Feb 19, 2020
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

Footer

© 2026 GitHub, Inc.