Conversation
Jarkko Sakkinen
jarkko
So what is going ATM with naked functions and Rust? Apparently it is still unstable. I don't really see what it could accomplish what could not be accomplished with global_asm!() macro tho.
Just looking into stuff related to my new job and also reasoning about Enarx, which I'm (still) interested to re-burnish once getting more into developing Rust again in my day job after 1.5 years break.
They share similarities as both delegate I/O to host and calculate in the guest and have predefined address space.
#rust #rustlang #antiguachicken
Just looking into stuff related to my new job and also reasoning about Enarx, which I'm (still) interested to re-burnish once getting more into developing Rust again in my day job after 1.5 years break.
They share similarities as both delegate I/O to host and calculate in the guest and have predefined address space.
#rust #rustlang #antiguachicken
1
1
0
@dngrs thanks but nope, more like wondering what keeps https://github.com/rust-lang/rust/issues/90957 open... i've been occasionally following this since 2022-23 when it was being considered for Enarx so there is nothing new to me. Just wondering what keeps the issue open up to date, since it has been a while.
It was not critical issue then and likely not now as global_asm!() allows to both write inline multi-line snippet of free form assembly code, or even include it from a file (refer to documentation). For me it would be at most cleaner syntax for common use cases (and better match with C's naked functions).
It was not critical issue then and likely not now as global_asm!() allows to both write inline multi-line snippet of free form assembly code, or even include it from a file (refer to documentation). For me it would be at most cleaner syntax for common use cases (and better match with C's naked functions).
1
0
0
Anatol
dngrs@chaos.social@jarkko Ah, I've posted the link because you were wondering about the differences to global_asm!; those are outlined in the document (more compiler guarantees)
1
0
0
@jarkko it's probably still open because not enough people have time to drag it over the finish line
1
0
0