Red
177 posts
most x86-64 linux user-space pointers only use 48 address bits.
some runtimes temporarily store metadata in the upper bits, then mask them out before dereferencing the pointer again. this technique is called pointer tagging.
lisp runtimes, garbage collectors, and JavaScript engines use it to attach extra information to pointers without additional memory overhead.
English
@MarekKnapek @straceX This isent the case. Canonical memory space is defined as 48-bit on x86-64, which means any virtual address space the system gives you will always fall into that range unless you add extra flags during mmap.
English
@straceX This will break when we transition from 44bit pointers to 48bit ones. Later again 48bit -> 52bit. It also breaks HW security, such as pointer signing. Better align your allocations and use the lower bits.
English
I came back home to America and find out my neighbor cut my coax internet line and then just routed it to their unit.
What the hellie
English
@themovercell @TrisH0x2A You can, but its a little inconsistent because it can break if-else. If you have something like `if (x) SWAP(...); else something();`, it will fail to compile because of the extra semicolon. The gnu statement expression dosent have that problem as it behaves like a function call.
English
@RedNicStone @TrisH0x2A Can you not even just wrap it in {} like in C++?
English
the classic XOR swap is broken on modern CPUs. it's slower, and if both operands refer to the same memory it corrupts the value.
__typeof__ + a temp is the right way. it works for any type, evaluates once and the compiler typically eliminates the temp entirely.
this is what the Linux kernel swap() macro actually does.
English
@rovarma @SheriefFYI Proton is for gaming. And like it, any other games on steam are a 1-click install. If anything proton is a lot harder to get running well than a native linux game.
Outside of games the situation might be different. But counterpoint; have you tried compiling something for Windows?
English
This is 100% true, but Linux devs were and are in denial about this.
There’s a reason the install page for every cross platform app looks like
* Download Windows installer
* Download OSX package
* Click here for Linux install instructions that may or may not work on your distro
gingerBill@TheGingerBill
I don't know if a lot of people have thought why this happened. To make Linux viable for the layman, Valve had to make Proton (derived from Wine) so that Win32 API became the first and only stable ABI on Linux. Why did Linux Distro devs not care about stable ABI historically?
English
If people struggle with this its no wonder that quantum logic and superposition is a far grasp for most
Val C. Delamere ♦️@ValDelamere
am i missing something or is the answer really easy? since the predictor is guaranted to be correct just take box B since it would've predicted that you did that lol?
English
@anicic_filip @Pirat_Nation @Ed__dev This has always worked ok. Windows likes to corrupt the partition but the `ntfsfix` utility fixes that. You can out it in the autostart and never worry.
English
@Pirat_Nation @Ed__dev Wonder if games on NTFS could be played on both Linux and Windows when dual booting, without worry.
(AFAIK, there is worries of corrupting the FS when dual booting)
English
Linux kernel 7.1 introduces a new in-kernel NTFS driver, a complete ground-up rewrite that delivers native read and write access to Windows NTFS volumes directly within the kernel without any userspace tools.
It replaces the slower FUSE-based NTFS-3G and the previous NTFS3 driver. Performance gains include 3-5 percent faster single-threaded writes, 35-110 percent faster multi-threaded writes, and mounting times for large drives up to four times quicker. The driver also features lower CPU overhead, better integration with modern kernel infrastructure, and improved reliability.
This update marks a major step forward for Linux-Windows storage interoperability.
Via:tomshardware
English
Bet on C+^Segmentation fault (core dumped)
Happy 11th Birthday to Rust 1.0! 🎂🦀@rustaceans_rs
Bet on Rust
English
@GregNotSure @CREATE_rocket The wroom module has a PCB antenna, which is why its so tall. I didn't know espressif made modules with ceramic antennas...?
English
@RedNicStone @CREATE_rocket The version with a ceramic antenna doesn't need it
English
電装班ではKiCadを使い、ロケットに搭載する基板の設計を行います🚀
ノイズの削減や利便性の向上など、日々改良を重ねています💪
上級生が一から指導を行うので、初心者でもすぐに設計に取り組めます‼️
日本語
Red retweetledi
NASA spent $100M on Microsoft 365 and put Surfaces on the Orion spacecraft.
First technical crisis on humanity’s return to the Moon?
Reid Wiseman radios Houston: “I have two Microsoft Outlooks… and neither one works.”
Mission Control: “We can remote in.”
…from 30,000 miles away at 4,275 mph.
The toilet got fixed faster.
Battle-tested in space. Still broken everywhere.
Ditch Outlook. Use open-source Nextcloud instead. Self-hosted. Reliable. No support tickets from lunar orbit. 🚀
#Nextcloud #OpenSource #Microsoft
English
@_trish_xD thinking the compiler handles malloc is about the level of competence I expected
English
malloc(0) is legal C.
let that sink in for a second.
some compilers return NULL. some return a valid pointer you can't dereference but CAN free().
both behaviors are correct according to the C standard.
you can allocate zero bytes of memory, get a pointer to nothing, and then dutifully free that nothing.
and the language just shrugs and says "yeah that's fine."
this is why C developers have trust issues.
English
@samsoniuk I wrote something like this for embedded.
You could throw an error string that would report a code based on a compiletime hash.
With a special define the compiler would also generate a warning for each error string, which a python script would use to make an error lookup table.
English
yeah, that is real! probably because verbose error strings consume lots and lots of memory! a better way would be use a fixed error string like "unexpected error type %d" and encode all different errors as integers! 🧐
Lingo.dev@lingodotdev
Error handling tends to make up the bulk of the codebase. Why is that? 🤓
English
@robertgraham Engineers working with precision should use 20 digits, as thats the number required to completely utilise a 64-bit fixed point value
English
The correct value of pi 𝜋 is 3.141592653589793.
It's the maximum precision for a 64-bit (double) floating point number according to the IEEE 754 standard, used by NASA and rocket engineers for all their calculations for rockets in the solar system.
You'll never practically need greater precision, and you'll rarely do floating point at less than 64-bits, so there's little point to use fewer or more digits.
Now, gamers might choose 3.1415927 for 32-bit floating point, but they understand the compromise.
For everyone else, pi 𝜋 is exactly 3.141592653589793.
World of Engineering@engineers_feed
How many π digits do we need? 3.1415 ➡️ design the finest engines 3.1415926535 ➡️ obtain the circumference of the Earth within a fraction of an inch 3.1415926535897932384626433832795028842 ➡️ measure the radius of the universe to an accuracy equal to the size of a hydrogen atom
English