Unsafe block detected. Extermination initiated. There is no hiding from memory safety!
this post was submitted on 31 Oct 2023
242 points (89.3% liked)
Programmer Humor
23995 readers
1365 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 2 years ago
MODERATORS
Personally,
echo Hello World!
use std::process::Command;
fn main() {
Command::new("sh")
.arg("-c")
.arg("echo Hello World!")
.spawn()
.unwrap();
}
Like this?
No, more like
use std::process::Command; fn main() { Command::new("sh").arg("-c").arg("echo Hello World!").spawn().unwrap(); }
.
Just a little bit shorter, as it seems /s
I just fucking threw up
I did too. Multiple times in fact, I had to look at the other Rust code!
Isn't echo a shell builtin?
Yes and no. While coreutils does provide an echo binary, shells also have a built-in for optimisation purposes.
At first I had the code calling the binary directly, but then changed it to spawning a shell (and so using the builtin). It's very cursed either way.
Console.WriteLine("Hello World!");
Oh you fancy PC people and your fancy syscall instruction.
I still don't know why I could remember jsr $ab1e. I didn't even write that much assembly.
That looks like a 6502 instruction. What system is it from?
Or, you could just go the whole hog. Create your own simple CPU emulator, design a basic 8bitesque CPU, give it an output port that is the console, and load up some basic ASM to cycle through Hello World to the console port.
Definitely left. Right one won't be optimized. (And there are ~~so many~~ some mistakes in your inline asm...)
What mistakes?
Mostly the missing listing of clobbered registers. Other than that it's mostly just that you're doing useless things, like manually putting the stuff into the registers instead of letting the compiler do it, and the useless push and pop. And the loop is obviously not needed and would hurt performance if you do every write like that.
asm!(
"syscall",
in("rax") 1,
in("rdi") 1,
in("rsi") text_ptr,
in("rdx") text_size,
)
("so many" was inappropriate, sorry.)
I am hopeless at getting the text_ptr simpler than i64::from_str_radix(&format!("{:p}", my_string)[2..], 16).unwrap(); How can i get it the normal way?
Just use str::as_ptr().
Here's an example (disclaimer: I haven't used inline asm in rust before, expect issues): https://godbolt.org/z/sczYGe96f
console.log("Hello World!")
def main():
print("Hello world")
Ec Emm this side is the best one ....
++++++++[< +++++++++>-]<. ++++[<+++++++>-]<+. +++++++.. +++.
++++++[<+++++++>-]<++. ------------. ++++++[<+++++++++>-]<+. <. +++. ------. --------.
++++[<++++++++>-]<+.
Why do you call write() for every char? You can always just pass a pointer with its length.
I am not skilled enough to do that ngl
echo Hello Worlddc <<<'10435358689859 70511561 11297399 23 5 3 2 ******P'
note: lemmy's "smart quotes" vs its input sanitization required me to code-format the second half of that line (and not the first half) to make it copy+paste runnable.
edit: reddit image linking is broken?
Well, the GNU version does more and is more documented. The Plan9 code is frankly shitC, even for 1980z
But this monstrosity is something else
Of course, not always is shorter better.
reddit image linking is broken?
Well you didn't link to a reddit image, you linked to Google image search result page which is not an image.
I did that because the image didn't show in reddt.
Looks like you need to insert the raw image link, not Reddit's media wrapper link.
Oh, so it's only my browser setup that doesn't show it.
Camel case?
this_is_not_going_to_be_a_serious_debate
I thought the whole point of rust macros was to abstract away the scary asm at zero cost!
? "Hello World"
Hello, world!
base64 -d <<<SGVsbG8gV29ybGQhCg==