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
A-codegenArea: Code generationA-runtimeArea: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflowsC-cleanupCategory: PRs that clean code up or issues documenting cleanup.
Upcalls are slowly being converted to rust. We'll want to convert rust_start (the runtime entry point) as well, and I think we're almost to the point where we can do this. Some difficulties:
It will run on a big native stack, so the compiler will have to set up the stack limit before main
Any call that requires the task pointer will fail hard. In particular this means we can't do any managed allocations
We can start by just immediately calling into the existing C++ rust_start function.
The text was updated successfully, but these errors were encountered:
r?
#3406
Pretty straightforward. I'm using opaque pointers instead trying to get trans and core to agree on the types of the main function and crate map. One oddity is that this required changing the order of the `-lrustrt` argument to the linker in order to resolve `upcall_new_stack`. Linkers are mysterious.
A-codegenArea: Code generationA-runtimeArea: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflowsC-cleanupCategory: PRs that clean code up or issues documenting cleanup.
Upcalls are slowly being converted to rust. We'll want to convert rust_start (the runtime entry point) as well, and I think we're almost to the point where we can do this. Some difficulties:
We can start by just immediately calling into the existing C++ rust_start function.
The text was updated successfully, but these errors were encountered: