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.

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

Need to compile Numba-CPU first to be able to compile Numba-GPU per #229 #236

Closed
ilhamv opened this issue Aug 18, 2024 · 2 comments
Closed
Assignees
Labels
gpu numba Numba-related issues

Comments

@ilhamv
Copy link
Collaborator

ilhamv commented Aug 18, 2024

This behavior shows up per #229, which factored local arrays and objects out to a dedicated local.py file to avoid problematic circular imports for future development

@ilhamv ilhamv added gpu numba Numba-related issues labels Aug 20, 2024
@ilhamv
Copy link
Collaborator Author

ilhamv commented Aug 23, 2024

Some finding that may be useful to debug:
If we start clean (no CPU/GPU cache at all), python input.py --mode=numba --target=gpu will fail (the error message seems to be the one for Numba-CPU), but the __ptxcache__ is still generated.
If we then do python input.py --mode=numba, it compiles and runs as usual.
If after that, we proceed with python input.py --mode=numba --target=gpu, which will use the existing __ptxcache__, it runs alright.

@ilhamv
Copy link
Collaborator Author

ilhamv commented Oct 15, 2024

This is addressed per #241

@ilhamv ilhamv closed this as completed Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
gpu numba Numba-related issues
Projects
None yet
Development

No branches or pull requests

2 participants