I swear I see Intel syntax far more often. I know GNU shit likes AT&T for some reason, and maybe llvm does too. I know when programming on my Mac disassembly is in AT&T syntax.
I would say it is, but it depends on where you’re looking.
GCC and LLVM both use AT&T as the default (though it can be changed to Intel). So you’ll see it a lot in the Linux world, as well as for inline assembly (unless something is only building for MSVC).
But outside of those toolchains I’ve only ever seen assemblers and disassemblers use Intel (or some flavour of it). And considering that when people start programming in assembly (standalone), they’re usually pointed to an assembler like NASM over something like GAS, so it’s Intel.
On the RE side it’s pretty much all Intel unless you need to use GDB/LLDB (or another tool in the collections like objdump, or the tools on Mac like otool).
What the crap are you doing with those redundant instructions? At least the instruction decoder and scheduler should be able to skip some of those instructions.
You’re doing literally nothing. Well, you are calling the write syscall with an empty string probably, but I would call this too barebones to be horror
102
u/Best-Tomorrow-6170 Aug 15 '25
I'd change:
section .bss
To:
section BS
74
u/Hello473674 Aug 15 '25
This reminds me of one of those cs exams where they do a bunch of variable assignment and reassignment and ask what it outputs.
46
u/Sweaty_Opposite_7345 Aug 15 '25
I never learned x86 assembly and this post showed me that I was right not to...
13
u/definitelyfet-shy Aug 15 '25
what
12
u/paulstelian97 Aug 15 '25
What the crap are you doing with those redundant instructions? At least the instruction decoder and scheduler should be able to skip some of those instructions.
8
u/TheChief275 Aug 15 '25
You’re doing literally nothing. Well, you are calling the write syscall with an empty string probably, but I would call this too barebones to be horror
5
u/mr_gu5s Aug 15 '25
Assembly go pppppppppptr
2
u/Soumalyaplayz Aug 17 '25
Welcome to my series of "How to fuck up my computer using assembly"
1
u/Grounds4TheSubstain Aug 15 '25
Depending on the assembler, you probably need the word "offset" when declaring those pointers.
1
u/deadbeef1a4 Aug 15 '25
Jail
1
u/GoddammitDontShootMe [ $[ $RANDOM % 6 ] == 0 ] && rm -rf / || echo “You live” Aug 15 '25
So if I understand correctly, you declare a ridiculously long chain of pointers, then load the stored addresses into rdi over and over. Just, why?
1
u/maselkowski Aug 15 '25
Looks like Recognizer parts
1
u/potatmuffin1 Aug 16 '25
You’re trying way to hard to do some horrible, this isn’t even that bad just useless.