Some old software does use 8-Bit ASCII for special/locale specific characters. Also there is this Unicode hack where the last bit is used to determine if the byte is part of a multi-byte sequence.
(_____(_____________(#)~~~~~~
Some old software does use 8-Bit ASCII for special/locale specific characters. Also there is this Unicode hack where the last bit is used to determine if the byte is part of a multi-byte sequence.
And then the rented Apartment is way too tiny for the price and was originally designed to house 2 people max. but now more than that have to share it. Bonus points if there is only 1 tiny bathroom with a bathtub/shower that’s from the late 80s and the kitchen is integrated into the already small living room.
Interesting feature, I had no idea. I just verified this with gcc and indeed the return register is always set to 0 before returning unless otherwise specified.
int main(void)
{
int foo = 10;
}
produces:
push %rbp
mov %rsp,%rbp
movl $0xa,-0x4(%rbp) # Move 10 to stack variable
mov $0x0,%eax # Return 0
pop %rbp
ret
int main(void)
{
int foo = 10;
return foo;
}
produces:
push %rbp
mov %rsp,%rbp
movl $0xa,-0x4(%rbp) # Move 10 to stack variable
mov -0x4(%rbp),%eax # Return foo
pop %rbp
ret
Unless your machine has error correcting memory. Then it will take literally forever.
Your CPU has big registers, so why not use them!
#include <x86intrin.h>
#include <stdio.h>
static int increment_one(int input)
{
int __attribute__((aligned(32))) result[8];
__m256i v = _mm256_set_epi32(0, 0, 0, 0, 0, 0, 1, input);
v = (__m256i)_mm256_hadd_ps((__m256)v, (__m256)v);
_mm256_store_si256((__m256i *)result, v);
return *result;
}
int main(void)
{
int input = 19;
printf("Input: %d, Incremented output: %d\n", input, increment_one(input));
return 0;
}
It doesn’t help that they keep deprecating and changing standard stuff every other version. It’s like they can’t make up their mind and everything may be subject to change. Updating to the most recent release can suddenly cause 10s or 100s of compiler warnings/errors and things may no longer behave the same. Then you look up the new documentation and realize that you have to refactor a large part of the codebase because the “new way” is for whatever reason vastly different.
“Remove them from power” by vooting you mean right? Right?
“unnamed source”
These machines are probably on their national intranet at most with no connection to the Internet. Still it’s weird. Whenever I watch KCTV and they show computer labs all of the PCs run some version of Win 7. Same with images they show on Voice of Korea. I have yet to see RedStarOS or GNU/Linux in general on DPRK media.
I’ve seen some that try to tell people that we currently have “chrony-capitalism” (or some other prefix that some “expert” came up with) perpetuated by a few bad apples up at top. Those are my personal favorite.
Exactly. Also someone can only release parts of the source code of their software and still license it under a permissive license like MIT, BSD, Apache, CDDL, etc. enabling them to claim that their software is “open source”. And usually in that case the released source code just so happens to mostly be wrapper/glue code that calls out into closed source binaries which is where the actual magic happens.
That’s only been my experience with software that depends on many different libraries. And it’s extra painful when you find out that it needs hyper specific versions of libraries that are older than the ones you have already installed. Rust is only painless because it just downloads all the right dependencies.