Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

nvptx-none-run.exp uses a hard-coded path to its lock file #7

Open
tschwinge opened this issue Jan 29, 2015 · 1 comment
Open

nvptx-none-run.exp uses a hard-coded path to its lock file #7

tschwinge opened this issue Jan 29, 2015 · 1 comment

Comments

@tschwinge
Copy link
Member

..., /tmp/nvptx-run, which may not be portable enough. On the other hand, the lock file really is meant to be system-wide. Perhaps use a lock backed by shm_open -- but that would have its own portability issues...
@tschwinge
Copy link
Member Author

With commit b1e277c "Replace 'nvptx-none-run-single' with a locking mechanism in 'nvptx-none-run.exp'", locking has moved into nvptx-none-run.exp, and the (changed) "default /tmp/gpu.lock may be overridden by setting the NVPTX_NONE_EXECUTION_LOCK_FILE environment variable".

@tschwinge tschwinge changed the title nvptx-none-run-single uses a hard-coded path to its lock file nvptx-none-run.exp uses a hard-coded path to its lock file Jul 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tschwinge