-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Comprehensive AOT Test Suite #5047
Comments
To make it easier to run on iOS and Android-style devices, I additionally propose this suite should have a single executable entrypoint; that makes it so that we just have to launch one executable, rather than one per test. |
This is an idea worth exploring, but with our current runtime setup it may be impractical or impossible, since some tests require custom runtime overrides, and the weak-linkage-replacement approach we have now makes that hard to do. (It also might make turnaround time unpleasant.) |
I think it'll be impossible if we try to do it for all tests, but I believe there's a large subset for which a single executable would help. I'm going to explore some possibilities and report back. |
It looks like it wouldn't actually be that necessary to have a single executable, as running via command line on a connected device is fast enough. |
Continuing discussion from #5040, Halide should have an AOT test suite for testing on devices/environments that don't support JIT. This could be a subset of the existing tests that use JIT compilation.
The text was updated successfully, but these errors were encountered: