Notices by sodiboo (sodiboo@gaysex.cloud)

@chjara@akko.wtf it's an endless stream~

@jessew@mk.cpluspatch.com @skye@void.rehab @thermia@sk.girlthi.ng evil

@jessew@mk.cpluspatch.com @skye@void.rehab @thermia@sk.girlthi.ng genuinely? how much we talkin

@skye@void.rehab @jessew@mk.cpluspatch.com @thermia@sk.girlthi.ng I would make such a good companion cube I'm like a little companion thing I can be your pet 🥺🥺 your little Nordic twinkdaughter pet 🥺🥺🥺

@jessew@mk.cpluspatch.com @skye@void.rehab @thermia@sk.girlthi.ng YAY TESTING

@jessew@mk.cpluspatch.com I will become a neet loser just to spite you

@jessew@mk.cpluspatch.com at this establishment?

the only FURNITURE I trust is that which smells of PEE

leaves out puppy treats for the suspiciously puppy shaped sharkey maintainers in my mutuals list

RE: https://gaysex.cloud/notes/a7i0yzgziezh0d7d

can a signal girl and a matrix girl really fall in love

nordic borders redrawn according to how well do i understand the language

@_r@donotsta.re this thing is beautiful

two reactions to seeing me wake up

wait holy shit I have ass wtf it's so nice to grab. why is it so fun to touch

@julia@eepy.moe isn't this just. a CPU. pretty sure modern CPUs do this (as long as the proceeding instructions aren't literally dependent on the result of this memory access)

@julia@eepy.moe like they'll reorder your instructions too. as long as you can't tell the difference between the result, anything goes. afaik on modern x86, if you make multiple independent calculations on a single register but overwrite it in-between, the CPU can and will realize they are independent, assign those instructions physically disjoint registers, and happily execute that shit out of order whilst waiting for a memory access that doesn't affect the results.

this is also, I believe (warning: hallucation) part of the reason why you have to be strict about multithreading and atomic access. because if you don't tell the CPU exactly how to coordinate this, then like. lol, lmao. good luck.

@julia@eepy.moe modern CPUs are literally just a hardware-accelerated JIT compiler with a memory-unsafe bytecode. branch prediction can and will assume things about your code that Isn't Always True and execute it as if it were (because that's faster), and that takes a huge performance hit when you *don't* meet that assumption (just like how in javascript if you suddenly pass a different type of arg, that call will be slower)

this is also why they come with so many side chain attacks and need security patches (microcode). it's a huge complex optimizing system and it's thanks to some FUCKING AWSOME and WILDLY IMPRESSIVE engineering efforts.

@jessew@mk.cpluspatch.com @starEyed@plasmatrap.com no thanks I think it would be funnier if I didn't do that and then your friend would think you were lying

@jessew@mk.cpluspatch.com @starEyed@plasmatrap.com not yet

spencer don't even follow me and is booping me on public.

boost this so spencer can see! hi spencer. boop