You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most of the remaining bugs seem to have to do with ccall and llvmcall. Here's a daring proposal: when we're constructing the framecode, what if we scan it and return Compiled() whenever we detect a :foreigncall or :llvmcall? That's basically just giving up on our optimizations that snip these out into separate functions; instead it says that any method that contains a ccall in it is one you can't step into.
Obviously this will reduce the number of methods accessible to JuliaInterpreter, but I've not noticed much of a chorus of "I can't step into this function" for the list of things we've added to compiled_methods. Of course this would expand them a lot, but 🤷?
The text was updated successfully, but these errors were encountered:
Most of the remaining bugs seem to have to do with ccall and llvmcall. Here's a daring proposal: when we're constructing the framecode, what if we scan it and return
Compiled()
whenever we detect a:foreigncall
or:llvmcall
? That's basically just giving up on our optimizations that snip these out into separate functions; instead it says that any method that contains accall
in it is one you can't step into.Obviously this will reduce the number of methods accessible to JuliaInterpreter, but I've not noticed much of a chorus of "I can't step into this function" for the list of things we've added to
compiled_methods
. Of course this would expand them a lot, but 🤷?The text was updated successfully, but these errors were encountered: