It's rather suspicious to leave normal handwriting out of the study, and makes me suspect bad faith.
718 karma · joined April 22, 2024
It's rather suspicious to leave normal handwriting out of the study, and makes me suspect bad faith.
People with this attitude are why the drains in my apartment keep backing up and my landlord sends emails threatening to evict whoever's flushing things they shouldn't.
With RISC-V, multiple instruction workarounds are needed for all of the above, and those sequences are usually sequentially dependent ones so they can't be run in parallel. i.e. the insanity of loading a 64-bit value through repeated 12-bit immediates with shifts, using multiple instructions to compute branch offsets, and RVV needing setvli instructions everywhere due to not having opcode space to encode vector length/type.
AArch64 is better, but still has problems with limited opcode space when it comes to future extensions. They've had to make "start mode" and "end mode" for SME to save on opcode space, and future compromises will likely be necessary.
Such as? I can't think of anything it does better for high performance cores.
Sometimes, you need to tell the designers NO. Moving background images don't help people figure out what the weather is going to be.
local x = condition ? value_a : value b
local x = condition and value_a or value_bWhat on earth is this supposed to mean?
Why do you think this rampant abuse is a good thing? What benefit does this provide to society?
What a weaselly way to put it.
A GPL library, as I'm sure you know, is perfectly usable by anyone including jujutsu and anyone else. They just have to also license under the GPL and this is no barrier to open source projects.
If not patching, what exactly would you call modifying part of the file?
They can't, so even PIC code still has to have a relocation table that gets patched. It's in a different page than the code though, so code does still get reused.
Editing to add: this deduplication is one of the greatest upsides to dynamic linking. Common libs like libgcc and libc only have to exist in memory once and can stay in CPU caches, whereas if they were statically linked into every binary, each binary would have a copy of that library that wouldn't be shared with anything else and you'd waste a lot of memory.
What did ISO give the JPEG XL team that made paywalling the standard worth it? Did ISO pay them or something?
https://metro.co.uk/2026/06/01/uk-considering-banning-kids-s...