-
Notifications
You must be signed in to change notification settings - Fork 15
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
JIT: Multiple compile
of different code crashes thorin
#134
Comments
PearCoding
added a commit
to PearCoding/artic
that referenced
this issue
Dec 6, 2022
This is indeed an Artic bug and will be fixed with the above PR. |
Hugobros3
added a commit
to AnyDSL/artic
that referenced
this issue
Dec 9, 2022
Closed with AnyDSL/artic#16 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Compiling two or more separate artic sources in JIT sometimes triggers the following assert:
The
rehash
function is called withnew_capacity=0
with the following stack trace stacktrace.txtIf the whole process is repeated again the error appears to be fixed. This is due to the cache ensuring the first source code is NOT compiled but only loaded again. The error is not triggered for all combinations of source code, but can be repeated (if the cache is disabled) with the same code combination.
I assume it is a
static
variable messing with something and not a memory space issue, as the memory usage is below 150Mb at the time of the event, which is way below the available 64Gb my computer has.Note: Both sources make use of CUDA kernels.
Note2: The first source is significantly smaller than the second source code.
Note3: Both code make usage of C functions outside the CUDA kernels.
Note4: The JIT process is NOT run in multiple threads, as the whole compile process is not thread safe.
Note5: The issue might be related to artic or the runtime. But the error got triggered in thorin, that is why it is posted here.
I will try to single out the issue and construct a small standalone example as the current issue is triggered in the Ignis framework.
The text was updated successfully, but these errors were encountered: