Dynamic count - how many times an opcode gets executed.
I. e. an instruction that doesn't appear often in code, but comes up in some hot loops (like encryption) would have low static and high dynamic.
1,072 karma · joined June 23, 2024
Dynamic count - how many times an opcode gets executed.
I. e. an instruction that doesn't appear often in code, but comes up in some hot loops (like encryption) would have low static and high dynamic.
Obviously, implementing one as a CMOS gate wouldn't be enough. Reversible gates would be very different. AFAIR they need to have a fan-out of one - you can't just wire an output to two inputs without losing reversibility.
On the other hand, ARM sells the cores to SoC vendors (and doesn't care much what becomes of it), SoC vendors ducktape the ARM cores to a bunch of Synopsys peripherals and sell the resulting SoCs to smartphone and car makers (and doesn't care much for the product). System integrators throw Android on top and sell it to the customers. Then Google, who get all the cream via Play, hides all the mess behind a thousand layers of Java abstractions.
DeviceTree is an offshot of Sun's OpenFirmware (and it leaves out all the hard stuff - OpenFirmware had Forth, DeviceTree expects the kernel to support every single brand of fan switch). OpenSBI is a disaster. I'm sorry, but what kind of bright mind came up with the idea of hiding damn *timer* behind a privilege switch? Timers were enough of a pain point on x86 already, then it settled on userspace-accesable RDTSC. RISC-V SBI? Reproducing x86 one stupid decision at a time.
* s/6/9/ Typo, thanks apothegm.
Market works well on non-correlated risky affairs with a positive expectation (i. e. Age of Discovery marine trade, where it all started). It can't do anything about a fundamentally negative-sum game.
Nothing is getting standardized across GPU vendors never ever again (pretty much every GPU uses some form of SIMD internally). Nvidia's CUDA is too specific to Nvidia's hardware, AMD have some serious problem delivering software/API part, Intel could but has too low of a market share, the rest are mobile IP core vendors with zero interest to provide compatibility.
is the last thing we need. Granted, picking a famous name you don't have any association with is an a-hole move. Not all a-hole moves should be illegal.
Sorry, that's about as far from truth as you can get. Threads were a thing way before multicore was available. Windows got them since Win95/NT4.0, and these didn't support multicore, nor did most of OpenVMS machines where NT thread model originated run multicore (were there any multicore VAXen at all). The two main points for threads back then was to simplify concurrent IO and to be able to run a background computation without hanging the UI. Unix was different because it was initially oriented towards timesharing aka. running a single program for user, so threads were seen as redundant complexity (as were async IO - so even today "I want to run something yet be able get more user input at any time" can sometimes be a PITA).
And year, not everything needs scalability. Scalability is actually actively harmful for everything that's not a server. E. g. UI needs to be responsive - but that doesn't necessary mean "run on multiple cores", rather "being able to preempt low-priority stuff". And usually you don't want to deal with multicore synchronization.
MCUs rarely have multiple cores. Yet multi-threading is ubiquitous, and on most RTOSes threads are much closer to "green threads" than Windows ones. Through as I keep screaming in every coroutine thread, I really wish C stackless coroutines were a thing, you can't afford a stack for everything.
There are more to this world than the boring AWS crud.
And I personally need kicad - it doesn't support Wayland at all because of some mouse-related stuff. Again, Wayland team thinks it's not their problem.
Then I had a lots of issues with a graphics tablet. Yes, it's a cheap chinesium knock-off, but it does work on X11. Wayland - no chance and it's obviously not their problem.
So I dropped Wayland altogether and went to X11/herbstluftwm. Was a few years ago, but I didn't bother to go back since - why should I? These aren't their problem, but now I don't use Wayland anymore, so these aren't my problem either.
What I'm trying to say, "hundreds of thousands of gamers stress-testing" have very little to say about usability. Yes the graphics part is excellent, nobody is denying that. There is more to a WM then graphics.
This. You need more than graphics to have a windowing system. Wayland team threw out X11, did graphics and left the rest for the others to figure out.