Replies: 1 comment
|
I was writing a tool in C++ to build a computational graph from a GUI and to JIT a kernel for executing that graph. Given the lack of introspection (yet) in the standard library, this has been a good part of the problem, since I want to avoid by-hand boilerplate in the tool I have been using up until now. And now I'm considering using Mojo for this, but it'd be essential in order to replicate that functionality that I could recompile the function implementing the graph based on what is in the UI, at runtime. I guess worst-case I could call out to the compiler as a process, embed mojo inside my application, etc., but it's an important usecase I feel. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
There are quite a few domains where being able to JIT compile computational kernels would make a lot of sense performance-wise either for capability expansion or in highly-dynamic-yet-specialized systems.
For instance, if one wants to provide their users with a way to write a custom kernel and feed it as-is (i.e. in source form) to the main AoTed program.
Science and engineering are also full of cases where you basically want to "
autotune" the very hot stuff at runtime right after a few important variables are set right at launch time. Telling people "please recompile after settingalias my_important_var = Nto the value that applies to your case" is not great.All reactions