Intel Nova Lake-S Rumored to Feature Up to 52 Cores
#CPUArchitecture #intel #MultiCoreProcessor #NovaLakeS #TechnologyUpgrades
https://blazetrends.com/intel-nova-lake-s-rumored-to-feature-up-to-52-cores/?fsp_sid=52792
#cpuarchitecture
Visual Transistor-level Simulation of the 6502 CPU
#HackerNews #VisualTransistorSimulation #6502CPU #RetroComputing #CPUArchitecture #HardwareSimulation
Hey #Intel and other hashtags!
What was your thoughts on #IntelItanium or #IA64 and what was your experience if you had any? I’ve not had any personal experience, but I’m curious to hear yours!
Can’t wait to read!
Hardware-Aware Coding: CPU Architecture Concepts Every Developer Should Know
https://blog.codingconfessions.com/p/hardware-aware-coding
#HackerNews #HardwareAwareCoding #CPUArchitecture #DeveloperInsights #CodingTips
The AnyCPU Illusion: Native Dependencies in .NET Applications
https://www.jocheojeda.com/2025/01/12/the-anycpu-illusion-native-dependencies-in-net-applications/
#dotnet #AnyCPU #nativeDependencies #crossPlatformDevelopment #ARMarchitecture #x64 #x86 #ARM64 #virtualization #WindowsOnARM #SQLServer #DevExpressXPO #EntityFrameworkCore #databaseDrivers #CPUarchitecture #liveDemo #applicationPortability #managedCode #fallbackStrategies #deployment #crossArchitectureSupport #CSharp
This CPU is FREE!
#CPU, #gaming, #risc-v, #riscv, #risc, #cpuarchitecture, #desktoppc, #ai, #machinelearning, #gamingpc, #pcgaming, #eurotrucksimulator2, #arm, #armprocessor, #apple, #mac, #linux, #fedora, #madeinchina2025, #chinesecpu, #chipfabrication
"Right now, 64-bit apps and operating systems are becoming the norm, rather than the exception, for Windows users. [...] Now, #Intel is starting to at least think about developing a #CPU architecture that just runs 64-bit apps and operating systems. The company quietly posted an update to its webpage with info, and a whitepaper on this 64-bit CPU, which it currently calls #x86S."
#CpuArchitecture #x86 #x64
https://www.neowin.net/news/intel-wants-feeback-for-a-proposed-64-bit-only-cpu-architecture-called-x86s/
Old and busted:
asymmetric CPU cores.
New and hot:
Asymmetric cache layout.
Seriously, writing good scheduler for everything from this to arm BIG.little and Intel's P-core/E-Core is a challenge where I am not sure how to properly solve it.
https://www.anandtech.com/show/18709/amd-unveils-ryzen-9-7950x3d-7900x3d-and-ryzen-7-7800x3d-up-to-128-mb-of-l3-cache-and-5-7-ghz-boost
#cpuarchitecture #scheduling #amd
Modern CPUs are Smarter Than You Might Realize
When it comes to programming, most of us write code at a level of abstraction that could be for a computer from the 1960s. Input comes in, you process it, and you produce output. Sure, a call to strcpy might work better on a modern CPU than on an older one, but your basic algorithms are the same. But what if there were ways to define your programs that would work better on modern hardware? That's what a pre-print book from [Sergey Slotin] answers.
As a simple example, consider the effects of branching on pipelining. Nearly all modern computers pipeline. That is, one instruction is fetching data while an older instruction is computing something, while an even older instruction is storing its results. The problem arises when you already have an instruction partially executed when you realize that an earlier instruction caused a branch to another part of your code. Now the pipeline has to be backed out and performance suffers while the pipeline refills. Anything that had an effect has to reverse and everything else needs to be discarded.
That's bad for performance. Because of this, some CPUs try to predict if a branch is likely to occur or not and then speculatively fill the pipeline for the predicted case. However, you can structure your code, for example, so that it is more obvious how branching will occur or even, for some compilers, explicitly inform the compiler if the branch is likely or not.
As you might expect, techniques like this depend on your CPU and you'll need to benchmark to show what's really going on. The text is full of graphs of execution times and an analysis of the generated assembly code for x86 to explain the results. Even something you think is a pretty good algorithm -- like binary search, for example, suffers on modern architectures and you can improve its performance with some tricks. Actually, it is interesting that the tricks work on GCC, but don't make a difference on Clang. Again, you have to measure these things.
Probably 90% of us will never need to use any of the kind of optimization you'll find in this book. But it is a marvelous book if you enjoy solving puzzles and analyzing complex details. Of course, if you need to squeeze those extra microseconds out of a loop or you are writing a library where performance is important, this might be just the book you are looking for. Although it doesn't cover many different CPUs, the ideas and techniques will apply to many modern CPU architectures. You'll just have to do the work to figure out how if you use a different CPU.
We've looked at pieces of this sort of thing before. Pipelining, for example. Sometimes, though, optimizing your algorithm isn't as effective as just changing it for a better one.
#softwaredevelopment #softwarehacks #cpuarchitecture #optimization
Where Are All The Cheap x86 Single Board PCs?
If we were to think of a retrocomputer, the chances are we might have something from the classic 8-bit days or maybe a game console spring to mind. It's almost a shock to see mundane desktop PCs of the DOS and Pentium era join them, but those machines now form an important way to play DOS and Windows 95 games which are unsuited to more modern operating systems. For those who wish to play the games on appropriate hardware without a grubby beige mini-tower and a huge CRT monitor, there's even the option to buy one of these machines new: in the form of a much more svelte Pentium-based PC104 industrial PC.
In A World Of Cheap Chips, Why No Intel?
Intel's Galileo and Edison boards hardly set the world of embedded computing on fire. Regi51, CC0.
Having a small diversion into the world of PC104 boards after a recent Hackaday piece it was first fascinating to see what 486 and Pentium-class processors and systems-on-chip are still being manufactured, but also surprising to find just how expensive the boards containing them can be. When an unexceptional Linux-capable ARM-based SBC can be had for under $10 it poses a question: why are there very few corresponding x86 boards with SoCs giving us the commoditised PC hardware we're used to running our mainstream distributions on? The answer lies as much in the story of what ARM got right as it does in whether x86 processors had it in them for such boards to have happened.
Imagine for a minute an alternative timeline for the last three decades. It's our timeline so the network never canned Firefly, but more importantly, the timeline of microprocessor evolution took a different turn as ARM was never spun out from Acorn and its architecture languished as an interesting niche processor found only in Acorn's Archimedes line. In this late 1990s parallel universe without ARM, what happened next?
Imagine the chain of events started by this early ARM chip never happened. Peter Howkins, CC BY-SA 3.0.
When Intel's Pentium was the dominant processor it seemed that a bewildering array of companies were fighting to provide alternatives. You'll be familiar with Intel, AMD, and Cyrix, and you'll maybe know Transmeta as the one-time employer of Linus Torvalds but we wouldn't be surprised if x86 offerings from the likes of Rise Technologies, NexGen, IDT, or National Semiconductor have passed you by.
This was a time during which RISC cores were generally regarded as the Next Big Thing, so some of these companies' designs were much more efficient hybrid RISC/CISC cores that debuted the type of architectures you'll find in a modern desktop x86 chip. We know that as the 1990s turned into the 2000s most of these companies faded away into corporate acquisition so by now the choice for a desktop is limited to AMD and Intel. But had ARM not filled the niche of a powerful low-power and low-cost processor core, would those also-ran processors have stepped up to the plate?
It's quite likely that they would have in some form, and perhaps your Raspberry Pi might have a chip from VIA or IDT instead of its Broadcom part. All those "Will it run Windows?" questions on the Raspberry Pi forums would be answered, and almost any PC Linux distro could be installed and run without problems. So given that all this didn't happen it's time to duck back into the real timeline. What did ARM get right, and what are the obstacles to an x86 Raspberry Pi or similar?
Sell IP, Win The Day
If you know one thing about ARM, it's that they aren't a semiconductor company as such. Instead they're a semiconductor IP company; you can't buy an ARM chip but instead you can buy chips from a host of other companies that contain an ARM core. By contrast the world of x86 has lacked a player prepared to so freely licence their cores, and thus the sheer diversity of the ARM market has not been replicated. With a fraction of the numbers of x86 SoC vendors compared to ones sporting ARM there simply isn't the cheap enough competition for those ten dollar boards.
Somewhere underneath all that heatsink is an x86 SBC.
Then there is the question of power. There is a tale of the very first ARM chip delivered to Acorn powering itself parasitically from the logic 1 signals on its bus when its power was disconnected, and whether true or not it remains that ARM processors have historically sipped power compared to even the most power-efficient of their x86 counterparts. Those x86 chips that do reach comparable power consumption are few and far between. Thus those small x86 boards that do exist will often have extravagant heatsink needs and power consumption figures compared to their ARM equivalents.
Bringing these two together, it creates a picture of a technology that's extremely possible to build but which brings with it an expensive chipset and support circuitry alongside a voracious appetite for power, factors which render it uncompetitive alongside its low-power and inexpensive ARM competition. If there's one thing about the world of technology though it's that it defies expectations, so could the chances of a accessible x86 platform ever increase? Probably not if it were left to AMD and Intel, but who's to say that an x86 softcore couldn't tip the balance. Only time will tell.
Header: Oligopolism, CC0.
#computerhacks #hardware #amd #cpuarchitecture #intel #raspberrypi #singleboardcomputer #x86
Here's a self- #introduction as suggested by @freemo !
#Photography (film and digital!)
#mathematics (proficiency level - Armchair)
#CPUArchitecture
#hardscifi
#weightlifting
#physics
#astronomy
#biohacking
#psychology
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst