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

Add warning to check_allocs(...) #49

Merged
merged 1 commit into from
Nov 20, 2023
Merged

Add warning to check_allocs(...) #49

merged 1 commit into from
Nov 20, 2023

Conversation

topolarity
Copy link
Member

@topolarity topolarity commented Nov 20, 2023

The results from check_allocs(foo, (...)) cannot strictly be expected to apply across Julia invocations or across any new method definitions (i.e. worlds). Furthermore, we don't have yet have sufficient testing to guarantee that our optimization pipeline in GPUCompiler will never diverge (however slightly) from the base Julia pipeline.

The unfortunate result is that we don't have the parity/stability guarantees we need from the Julia compiler to use check_allocs(foo, ...) for allocation-free guarantees at runtime.

This adds a note to clarify that such a usage is unsound.

This function is useful for investigation and optimization, but we don't
have sufficient parity/stability guarantees from the Julia compiler to
use it for allocation-free guarantees at runtime.

This adds a note to clarify that such a usage is _unsound_.
@topolarity topolarity mentioned this pull request Nov 20, 2023
@topolarity topolarity merged commit 48a8c34 into main Nov 20, 2023
5 checks passed
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.

1 participant