Yes, sorry I remembered incorrectly.
The rust compiler claims to be i686 and the CPU is i686 too, but the rust compiler is using Pentium 4 only instructions so it doesn't actually work for i686.
Edit: I see from the sister post that it is actually llvm and not rust, so I'm half barking up the wrong tree. But somehow this is not an issue with gcc and friends.
It's not just that, current sentiment around the CFAA is that any kind of unsanctioned third-party user agent for anything that isn't the open web is potentially prosecutable. Plus, if the big user platforms decide they don't like some aspect of what you're doing, they will shut down all of your access, and potentially access of others close to you, everywhere, and aggressively prevent you from reestablishing even a baseline of inoffensive participation, at great potential cost to your well-being.
Isn't it usually one bill, but an omnibus bill? My understanding is that the actual guard rail that the US congress has discarded is requiring that the contents of the bill be limited to the purview described by the bill's title.
I guess technically yeah but they're usually bills that wouldn't have any chance of being law on their own. "I'll vote for it if you include this" kinda deals.
At one point laptop wifi cards seemed to mostly be m.2 cards, which, while not usually trivial, were relatively feasible to swap out. Has that changed?
I hate that curl $SOMETHING | sh has become normalized. One does not _have_ to blindly pipe something to a shell. It's quite possible to pull the script in a manner that allows examination. That Homebrew also endorses this behaviour doesn't make it any less of a risky abdication of administrative agency.
But then I'm a weirdo that takes personal offense at tools hijacking my rc / PATH, and keep things like homebrew at arm's length, explicitly calling shellenv when I need to use it.
Has something changed that allows a more relaxed refcounting / less eager "gc"? Py_DECREF was what murdered any hope of performance back when we hooked up 3.3 to OMR... Well that and the complete opacity of everything implemented in C
I don't know how any baseball fan can be against this. I would bet that man has made at least one season-ending mistake on every team out there throughout his career, and he's completely unapologetic and arrogant about it. Everyone was relieved when he retired, but there's been plenty of others happy to play the king villain now.
Was this compiled at O0? The generated code looks unnecessarily long-winded - at the very least I would expect the match jump table to get culled to only the Relaxed implementation.
> Note we did not ask rustc to optimize the code. If we did, the compiler would generate more efficient assembly: No spills to the stack, fewer jumps, no dispatch on memory ordering, etc. But I wanted to keep the output as close to the original IR as possible to make it easier to follow.
Wikipedia seems to correlate: https://en.wikipedia.org/wiki/Pentium_Pro, as do discussions on CMOV: https://stackoverflow.com/a/4429563