Wen<p>Novel computing structures</p><p>"They could become competitive in specialized domains such as edge AI, neuromorphic systems, or flexible electronics,"</p><p>Somewhat niche I suspect for most here 🤨 but still a fascinating achievement. Difficult to see where it will find use on a large scale though.</p><p><a href="https://www.theregister.com/2025/06/16/penn_state_boffins_2d_cmos/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">theregister.com/2025/06/16/pen</span><span class="invisible">n_state_boffins_2d_cmos/</span></a></p><p><a href="https://mastodon.scot/tags/ComputerArchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ComputerArchitecture</span></a> <a href="https://mastodon.scot/tags/Novelty" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Novelty</span></a> <a href="https://mastodon.scot/tags/Innovation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Innovation</span></a></p>
Recent searches
No recent searches
Search options
Only available when logged in.
mastodon.ie is one of the many independent Mastodon servers you can use to participate in the fediverse.
Irish Mastodon - run from Ireland, we welcome all who respect the community rules and members.
Administered by:
Server stats:
1.6Kactive users
mastodon.ie: About · Profiles directory · Privacy policy
Mastodon: About · Get the app · Keyboard shortcuts · View source code · v4.3.9
#computerarchitecture
0 posts · 0 participants · 0 posts today
Silicon Underground (Dave F)<p>On April 2, 1997, AMD released a new CPU. If it succeeded, AMD had a chance at success. If it failed, AMD would probably fail with it. That CPU was the K6, and it revitalized AMD, letting them move to the middle of the market, where margins were high enough to fund its future CPUs. <a href="https://ioc.exchange/tags/RetroComputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RetroComputing</span></a> <a href="https://ioc.exchange/tags/TechHistory" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TechHistory</span></a> <a href="https://ioc.exchange/tags/ComputerArchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ComputerArchitecture</span></a> <a href="https://ioc.exchange/tags/Innovation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Innovation</span></a> <a href="https://ioc.exchange/tags/TechMilestones" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TechMilestones</span></a> <a href="https://ioc.exchange/tags/1990sTech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>1990sTech</span></a> <a href="https://dfarq.homeip.net/amd-k6-released-april-2-1997/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">dfarq.homeip.net/amd-k6-releas</span><span class="invisible">ed-april-2-1997/</span></a></p>
Cristian<p>¿Algún experto en sistemas operativos o en arquitectura de computadores me puede comprobar que este diagrama es correcto? Lo acabo de crear en <span class="h-card" translate="no"><a href="https://hostux.social/@drawio" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>drawio</span></a></span> partiendo de varios gráficos de "Sistemas Operativos" de Gary Nutt (Ed. Pearson).</p><p>¡Mil gracias!</p><p><a href="https://mastodon.social/tags/OS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OS</span></a> <a href="https://mastodon.social/tags/computerarchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>computerarchitecture</span></a> <a href="https://mastodon.social/tags/software" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>software</span></a> <a href="https://mastodon.social/tags/hardware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>hardware</span></a></p>
Silicon Underground (Dave F)<p>Intel released a new CPU on March 22, 1993. Instead of a part number, it had a brand name. Calling it Pentium instead of 586 helped Intel's problem with clones. <a href="https://dfarq.homeip.net/what-came-after-486/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">dfarq.homeip.net/what-came-aft</span><span class="invisible">er-486/</span></a> <a href="https://ioc.exchange/tags/CPUHistory" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CPUHistory</span></a> <a href="https://ioc.exchange/tags/ComputerArchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ComputerArchitecture</span></a> <a href="https://ioc.exchange/tags/Innovation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Innovation</span></a> <a href="https://ioc.exchange/tags/TechThrowback" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TechThrowback</span></a> <a href="https://ioc.exchange/tags/1990sTech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>1990sTech</span></a> <a href="https://ioc.exchange/tags/Microprocessors" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Microprocessors</span></a> <a href="https://ioc.exchange/tags/RetroComputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RetroComputing</span></a></p>
Tuomas Väisänen 📼🧟♂️<p>Hey everyone involved in <a href="https://vis.social/tags/ComputerScience" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ComputerScience</span></a>, are you looking for a <a href="https://vis.social/tags/job" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>job</span></a> in <a href="https://vis.social/tags/academia" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>academia</span></a>?</p><p>Aalto University in Finland has several positions open for assistant professors. The topics include <a href="https://vis.social/tags/MachineLearning" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MachineLearning</span></a>, <a href="https://vis.social/tags/Programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Programming</span></a>, <a href="https://vis.social/tags/ComputerArchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ComputerArchitecture</span></a>, <a href="https://vis.social/tags/CyberSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CyberSecurity</span></a>, <a href="https://vis.social/tags/SoftwareEngineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SoftwareEngineering</span></a> and Human-Computer Interactions.</p><p><a href="https://www.aalto.fi/en/department-of-computer-science/assistant-professor-positions" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">aalto.fi/en/department-of-comp</span><span class="invisible">uter-science/assistant-professor-positions</span></a></p>
Stephen Hoffman<p>If it's not an API, it's an implementation detail.</p><p>A nicely-phrased distinction: “On the technical side, I want to stress that there’s no such thing as an undocumented API (or private API). By definition an API is something that’s meant to be called by apps. Things that aren’t APIs are implementation details. And when you use that term it’s easier to evaluate your choices.” — Quinn “The Eskimo!”</p><p>Which is all too reminiscent of a common outcome among apps:</p><p>"With a sufficient number of users of an API,<br>it does not matter what you promise in the contract:<br>all observable behaviors of your system<br>will be depended on by somebody.” — Hyrum's Law</p><p>Platform providers would usually prefer to follow the model “Everything which is not allowed is forbidden" while developers are fond of "Everything which is not forbidden is allowed”.* The former avoids breaking quite as many apps and can deeply annoy, err, limit app developers, while following the latter makes non-breaking platform changes difficult to impossible, and increases support and testing.</p><p>At the intersection of those two models is app instability, angst, and architectural limits.</p><p>And yes, there are inevitably cases where API designs are just broken, or where the designs reach their architectural limits, and those then either stymy further work, or might get incompatibly un-broken, or preferably get replaced in parallel with better and more capable designs and the older APIs deprecated and removed. </p><p>How you design replacements for your API limits is part of your design too, but a part frequently ignored. As are app upgrades.</p><p>Limited API designs I've met have included an eight-byte password hash buffer, and APIs featuring 32-bit addressing for storage and memory.</p><p>*I'll leave any discussions of Misters Dillon and Cooley for another time.</p><p><a href="https://infosec.exchange/tags/computerarchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>computerarchitecture</span></a> <a href="https://infosec.exchange/tags/appdev" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>appdev</span></a> <a href="https://infosec.exchange/tags/compatibility" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>compatibility</span></a> <a href="https://infosec.exchange/tags/PlatformEngineering" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>PlatformEngineering</span></a> <a href="https://infosec.exchange/tags/appdesign" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>appdesign</span></a></p>
Stephen Hoffman<p><span class="h-card" translate="no"><a href="https://mstdn.ca/@jfmezei" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>jfmezei</span></a></span> :How long are data blocks for each entry in the in-CPU cache? 64 bits ? 128 bytes ? 1 page ? </p><p>It varies. Most implementations will use one cache block size at a time at a given cache level, but that size and the size and the organization of the caches varies.</p><p>:Does this vary from architecture to architecture or even inside an architecture? </p><p>Yes. Alpha caching varied by processor and by implementation, all within the limits of the Alpha architecture.</p><p>:Is it totally transparent when writing at OS level?</p><p>Totally transparent? No.</p><p>Details, such as what was locally called word tearing, alignment, memory timing, and memory lock processing, all get involved. </p><p>Similar requirements can arise in apps.</p><p>There are a few other wrinkles I’d prefer to not meet again, too.</p><p>Mostly transparent? Yes.</p><p>:And in multi core with coherent caches, when a core does a write to RAM, does memory controller propagate this to all other cores in case they have it cached? or does memory controller know which core has what in cache and send only relevant updates?</p><p>It depends. Most of what I’ve met will mark the cache contents as being invalid, and will await the next opportunity to wait for main memory to load the data, or to wait for a load from L3, or such. I can’t recall ever working on a cache-coherent multiprocessor that tried to reload the cache everywhere.</p><p>Alpha could load cache speculatively, or explicitly, or evict as needed.</p><p><a href="http://bitsavers.org/pdf/dec/alpha/system_reference/Alpha_System_Reference_Manual_Version_7_1997.pdf" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">http://</span><span class="ellipsis">bitsavers.org/pdf/dec/alpha/sy</span><span class="invisible">stem_reference/Alpha_System_Reference_Manual_Version_7_1997.pdf</span></a></p><p>WP has a reasonable description, as well: </p><p><a href="https://en.wikipedia.org/wiki/Cache_(computing)" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">en.wikipedia.org/wiki/Cache_(c</span><span class="invisible">omputing)</span></a></p><p>Deeper still:</p><p><a href="https://www.cs.swarthmore.edu/~kwebb/cs31/f18/memhierarchy/caching.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">cs.swarthmore.edu/~kwebb/cs31/</span><span class="invisible">f18/memhierarchy/caching.html</span></a></p><p>More for amusement, figures 5 and 6 nicely show the shifting scale of the complexity of modern computer systems:</p><p><a href="https://www.computer.org/csdl/journal/ts/2021/06/08704965/19HKUhJMVAQ" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">computer.org/csdl/journal/ts/2</span><span class="invisible">021/06/08704965/19HKUhJMVAQ</span></a></p><p><a href="https://infosec.exchange/tags/digitalequipment" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>digitalequipment</span></a> <a href="https://infosec.exchange/tags/dec" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dec</span></a><br><a href="https://infosec.exchange/tags/alpha" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>alpha</span></a> <a href="https://infosec.exchange/tags/computerarchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>computerarchitecture</span></a> <a href="https://infosec.exchange/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>retrocomputing</span></a></p>
Science News<p>Energy-efficient memory innovation: SOT-MRAM <a href="https://idw-online.social/tags/MemoryTechnology" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MemoryTechnology</span></a> could replace cache memory in <a href="https://idw-online.social/tags/ComputerArchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ComputerArchitecture</span></a> in the future // <a href="https://idw-online.social/tags/SustainableComputing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SustainableComputing</span></a> <a href="https://idw-online.social/tags/SOTMRAM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SOTMRAM</span></a> <a href="https://idw-online.social/tags/SpinOrbitTorque" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SpinOrbitTorque</span></a> <a href="https://idw-online.social/tags/OrbitalHallEffect" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OrbitalHallEffect</span></a> @NatureComms @ERC_Research @HorizonEU <a href="https://idw-online.social/tags/MainzUniversity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MainzUniversity</span></a> <br><a href="https://nachrichten.idw-online.de/2025/02/06/toward-sustainable-computing-energy-efficient-memory-innovation" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">nachrichten.idw-online.de/2025</span><span class="invisible">/02/06/toward-sustainable-computing-energy-efficient-memory-innovation</span></a></p>
Jure Repinc :linux: :kde:<p>Inside SiFive’s P550 Microarchitecture<br>🔗 <a href="https://old.chipsandcheese.com/2025/01/26/inside-sifives-p550-microarchitecture/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">old.chipsandcheese.com/2025/01</span><span class="invisible">/26/inside-sifives-p550-microarchitecture/</span></a></p><p>"The P550 is a 3-wide out-of-order core with a 13 stage pipeline. Out-of-order execution lets the core move past a stalled instruction to extract instruction level parallelism. It’s critical for achieving high performance because cache and memory latency can be significant limiters for modern CPUs."</p><p><a href="https://mstdn.io/tags/RISCV" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RISCV</span></a> <a href="https://mstdn.io/tags/RISC_V" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RISC_V</span></a> <a href="https://mstdn.io/tags/ComputerArchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ComputerArchitecture</span></a> <a href="https://mstdn.io/tags/CPU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CPU</span></a> <a href="https://mstdn.io/tags/CPUs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CPUs</span></a> <a href="https://mstdn.io/tags/Processor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Processor</span></a> <a href="https://mstdn.io/tags/Processors" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Processors</span></a> <a href="https://mstdn.io/tags/Hardware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Hardware</span></a> <a href="https://mstdn.io/tags/ComputerHardware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ComputerHardware</span></a> <a href="https://mstdn.io/tags/Eswin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Eswin</span></a> <a href="https://mstdn.io/tags/EC7700X" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>EC7700X</span></a> <a href="https://mstdn.io/tags/SiFive" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SiFive</span></a> <a href="https://mstdn.io/tags/P550" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>P550</span></a></p>
Jure Repinc :linux: :kde:<p>RISC-V Vector Extension overview<br>🔗 <a href="http://0x80.pl/notesen/2024-11-09-riscv-vector-extension.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">http://</span><span class="ellipsis">0x80.pl/notesen/2024-11-09-ris</span><span class="invisible">cv-vector-extension.html</span></a></p><p>"The goal of this text is to provide an overview of RISC-V Vector extension (RVV), and compare — when applicable — with widespread SIMD vector instruction sets: SSE, AVX, AVX-512, ARM Neon and SVE.<br>[…]<br>The vector extension is quite a huge addition. It adds 302 instructions plus four highly configurable load & store operations."</p><p><a href="https://mstdn.io/tags/RISCV" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RISCV</span></a> <a href="https://mstdn.io/tags/RISC_V" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RISC_V</span></a> <a href="https://mstdn.io/tags/RVV" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RVV</span></a> <a href="https://mstdn.io/tags/ComputerArchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ComputerArchitecture</span></a> <a href="https://mstdn.io/tags/ISA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ISA</span></a> <a href="https://mstdn.io/tags/InstructionSetArchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>InstructionSetArchitecture</span></a> <a href="https://mstdn.io/tags/CPU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CPU</span></a> <a href="https://mstdn.io/tags/CPUs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CPUs</span></a> <a href="https://mstdn.io/tags/processor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>processor</span></a> <a href="https://mstdn.io/tags/processors" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>processors</span></a></p>
Yaroslav Khnygin<p>Bob Supnik breaks the CVAX to make COBOL run faster:</p><p><a href="https://mastodon.ie/tags/DEC" class="mention hashtag" rel="tag">#<span>DEC</span></a> <a href="https://mastodon.ie/tags/Digital" class="mention hashtag" rel="tag">#<span>Digital</span></a> <a href="https://mastodon.ie/tags/DigitalEquipmentCorporation" class="mention hashtag" rel="tag">#<span>DigitalEquipmentCorporation</span></a> <a href="https://mastodon.ie/tags/VAX" class="mention hashtag" rel="tag">#<span>VAX</span></a> <a href="https://mastodon.ie/tags/CVAX" class="mention hashtag" rel="tag">#<span>CVAX</span></a> <a href="https://mastodon.ie/tags/COBOL" class="mention hashtag" rel="tag">#<span>COBOL</span></a> <a href="https://mastodon.ie/tags/ComputerArchitecture" class="mention hashtag" rel="tag">#<span>ComputerArchitecture</span></a> <a href="https://mastodon.ie/tags/ComputerHistory" class="mention hashtag" rel="tag">#<span>ComputerHistory</span></a> <a href="https://mastodon.ie/tags/ComputingHistory" class="mention hashtag" rel="tag">#<span>ComputingHistory</span></a> <a href="https://mastodon.ie/tags/ComputerHistoryMuseum" class="mention hashtag" rel="tag">#<span>ComputerHistoryMuseum</span></a> <a href="https://mastodon.ie/tags/CHM" class="mention hashtag" rel="tag">#<span>CHM</span></a> <a href="https://mastodon.ie/tags/BobSupnik" class="mention hashtag" rel="tag">#<span>BobSupnik</span></a></p>
Alfa 🏳️⚧️<p><a href="https://tech.lgbt/tags/introduction" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>introduction</span></a> <a href="https://tech.lgbt/tags/house" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>house</span></a> <a href="https://tech.lgbt/tags/housemd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>housemd</span></a> <a href="https://tech.lgbt/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>programming</span></a> <a href="https://tech.lgbt/tags/computerarchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>computerarchitecture</span></a> <a href="https://tech.lgbt/tags/computerscience" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>computerscience</span></a> <a href="https://tech.lgbt/tags/compsci" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>compsci</span></a> <a href="https://tech.lgbt/tags/breakingbad" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>breakingbad</span></a> <a href="https://tech.lgbt/tags/ultrakill" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ultrakill</span></a> <a href="https://tech.lgbt/tags/speedrun" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>speedrun</span></a> <a href="https://tech.lgbt/tags/transbian" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>transbian</span></a> <a href="https://tech.lgbt/tags/transfem" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>transfem</span></a> <a href="https://tech.lgbt/tags/EldenRing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>EldenRing</span></a> <br>so here goes nothing.<br>I'm a 20 yr old trans woman who's learning comp sci at Reykjavík University, I'm highly interested in computer science and more generally computer architecture (at least currently). <br>My main interests besides computer science are music and then i flip between BB universe and House M.D<br>Whenever I find a new obsession I get very very hyper-focused on it and will spend the next month basically only focusing on it. I tend to play ULTRAKILL about bi-monthly, I speedrun the game a bit, it's one of my main interests. I also play a lot of (too much) elden ring, I've beaten it around 5-6 times at this point(still havent beaten the final boss of the dlc tho...)<br>Follow if you have any of these interests</p>
रञ्जित (Ranjit Mathew)<p>“ARM Or x86? ISA Doesn’t Matter” [2021], Chips And Cheese (<a href="https://chipsandcheese.com/2021/07/13/arm-or-x86-isa-doesnt-matter/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">chipsandcheese.com/2021/07/13/</span><span class="invisible">arm-or-x86-isa-doesnt-matter/</span></a>).</p><p>Via HN: <a href="https://news.ycombinator.com/item?id=41368004" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">news.ycombinator.com/item?id=4</span><span class="invisible">1368004</span></a></p><p><a href="https://mastodon.social/tags/ISA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ISA</span></a> <a href="https://mastodon.social/tags/Hardware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Hardware</span></a> <a href="https://mastodon.social/tags/CPU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CPU</span></a> <a href="https://mastodon.social/tags/ARM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ARM</span></a> <a href="https://mastodon.social/tags/Intel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Intel</span></a> <a href="https://mastodon.social/tags/AMD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AMD</span></a> <a href="https://mastodon.social/tags/x86" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>x86</span></a> <a href="https://mastodon.social/tags/RISCV" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RISCV</span></a> <a href="https://mastodon.social/tags/Performance" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Performance</span></a> <a href="https://mastodon.social/tags/ComputerArchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ComputerArchitecture</span></a> <a href="https://mastodon.social/tags/InstructionSet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>InstructionSet</span></a></p>
µP<p><a href="https://mastodon.social/tags/BASIC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BASIC</span></a> <a href="https://mastodon.social/tags/ComputerArchaeology" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ComputerArchaeology</span></a> <a href="https://mastodon.social/tags/computerarchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>computerarchitecture</span></a></p>
Jure Repinc :linux: :kde:<p>RISC-V State of the Union — current highlights and roadmap of RISC-V by RISC-V's chief architect<br>🎞 <a href="https://yewtu.be/watch?v=_oLVPFQvJbI" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">yewtu.be/watch?v=_oLVPFQvJbI</span><span class="invisible"></span></a><br>Slides: <a href="https://riscv-europe.org/summit/2024/media/proceedings/plenary/Tue-11-30-Krste-Asanovic.pdf" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">riscv-europe.org/summit/2024/m</span><span class="invisible">edia/proceedings/plenary/Tue-11-30-Krste-Asanovic.pdf</span></a></p><p><a href="https://mstdn.io/tags/RISCV" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RISCV</span></a> <a href="https://mstdn.io/tags/RISC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RISC</span></a> <a href="https://mstdn.io/tags/CPU" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CPU</span></a> <a href="https://mstdn.io/tags/CPUs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CPUs</span></a> <a href="https://mstdn.io/tags/architecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>architecture</span></a> <a href="https://mstdn.io/tags/ComputerArchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ComputerArchitecture</span></a> <a href="https://mstdn.io/tags/processor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>processor</span></a> <a href="https://mstdn.io/tags/processors" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>processors</span></a> <a href="https://mstdn.io/tags/ISA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ISA</span></a> <a href="https://mstdn.io/tags/InstructionSetArchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>InstructionSetArchitecture</span></a> <a href="https://mstdn.io/tags/hardware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>hardware</span></a></p>
Greg Lloyd<p>Great <a href="https://federate.social/tags/ConnectionMachine" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ConnectionMachine</span></a> + <a href="https://federate.social/tags/Feynman" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Feynman</span></a> story!</p><p>“By the end of that summer of 1983, Richard had completed his analysis of the behavior of the router, and much to our surprise and amusement, he presented his answer in the form of a set of partial differential equations. To a physicist this may seem natural, but to a computer designer, treating a set of boolean circuits as a continuous, differentiable system is a bit strange.”</p><p><a href="https://federate.social/tags/computerhistory" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>computerhistory</span></a> <a href="https://federate.social/tags/computerarchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>computerarchitecture</span></a> <a href="https://mastodon.scot/@simon_brooke/112354279945181945" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">mastodon.scot/@simon_brooke/11</span><span class="invisible">2354279945181945</span></a></p>
Greg Lloyd<p><span class="h-card" translate="no"><a href="https://mastodon.social/@spiralganglion" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>spiralganglion</span></a></span> 🧵CM-1 history </p><p>Thank you for posting your thread! </p><p>I particularly enjoyed Tamiko Thiel’s 1992 + revised ‘The Design of the Connection Machine’ article. </p><p><a href="https://federate.social/tags/computerarchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>computerarchitecture</span></a><br><a href="https://federate.social/tags/computerhistory" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>computerhistory</span></a></p><p><a href="https://tamikothiel.com/theory/cm_txts/index.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">tamikothiel.com/theory/cm_txts</span><span class="invisible">/index.html</span></a></p>
रञ्जित (Ranjit Mathew)<p>Both <a href="https://mastodon.social/tags/TheChipLetter" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TheChipLetter</span></a> & <a href="https://mastodon.social/tags/CompilerExplorer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>CompilerExplorer</span></a> are awesome, if you're interested in <a href="https://mastodon.social/tags/programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>programming</span></a>, <a href="https://mastodon.social/tags/ComputerArchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ComputerArchitecture</span></a>, <a href="https://mastodon.social/tags/hardware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>hardware</span></a>, or <a href="https://mastodon.social/tags/compilers" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>compilers</span></a>:</p><p>"Compiler Explorer", 'Babbage' (<a href="https://thechipletter.substack.com/p/compiler-explorer" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">thechipletter.substack.com/p/c</span><span class="invisible">ompiler-explorer</span></a>).</p><p>On HN: <a href="https://news.ycombinator.com/item?id=40357139" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">news.ycombinator.com/item?id=4</span><span class="invisible">0357139</span></a></p><p><a href="https://mastodon.social/tags/Godbolt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Godbolt</span></a> <a href="https://mastodon.social/tags/MattGodbolt" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MattGodbolt</span></a> <a href="https://mastodon.social/tags/Optimization" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Optimization</span></a></p>
Beej 💾<p>Lots of information on how microchips work.</p><p><a href="https://exclusivearchitecture.com/03-technical-articles-IC-00-table-of-contents.html" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://</span><span class="ellipsis">exclusivearchitecture.com/03-t</span><span class="invisible">echnical-articles-IC-00-table-of-contents.html</span></a></p><p><a href="https://mastodon.sdf.org/tags/computerarchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>computerarchitecture</span></a> <a href="https://mastodon.sdf.org/tags/cpu" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cpu</span></a></p>
Stephen Hoffman<p><span class="h-card" translate="no"><a href="https://mstdn.ca/@jfmezei" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>jfmezei</span></a></span> Assembler floating point? Some. </p><p>OpenVMS didn’t have any FP in the kernel when last I checked, and the operating system drivers didn’t have FP.</p><p>Whole lot of integer, though.</p><p>There was more than a little FP code in the distribution kit in user mode, though.</p><p>And in the compilers, obviously.</p><p>I don’t know off-hand what the graphics drivers were doing with FP, if anything.</p><p>There was a fifty-some page design and detail spec created for the Alpha-to-Itanium port, around floating point. Most of the hassles there involved the migration of existing code and data to IEEE floating point, or of using newly-created routines that emulated VAX FP on Itanium. Alpha had both IEEE and VAX FP, so various existing code was not switched. Itanium used IEEE and lacked VAX FP.</p><p>Amusingly, it was possible for a faulty floating point accelerator to cause the VAX/VMS kernel to bugcheck in the lock manager though, as occasionally happened with FP780 on VAX-11/780. This bugcheck even though the lock manager had no floating point, it did have integer multiply, and FP780 also accelerated integer multiply. Hence, boom.</p><p>Ignoring shaders whether Apple Metal or otherwise, and ignoring OpenCL and other such code, and ignoring other GPU-accelerated processing, and ignoring co-processor boards, all which can do their own thing with their own processing, I/O controllers only deal with the *host* instruction set when the host is executing something from the controller firmware store (think “ROM”), whether that’s native instructions or something else like EFI (UEFI) byte code. </p><p><a href="https://developer.apple.com/metal/shader-converter/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">developer.apple.com/metal/shad</span><span class="invisible">er-converter/</span></a></p><p><a href="https://en.wikipedia.org/wiki/OpenCL" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">en.wikipedia.org/wiki/OpenCL</span><span class="invisible"></span></a></p><p><a href="https://uefi.org/specs/UEFI/2.10/22_EFI_Byte_Code_Virtual_Machine.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">uefi.org/specs/UEFI/2.10/22_EF</span><span class="invisible">I_Byte_Code_Virtual_Machine.html</span></a></p><p>See also CUDA, Vulkan, DirectX, etc.</p><p>TL;DR: the design of modern computers has shifted substantially from the simplistic scattering-of-boxes conceptual descriptions that were (and still are?) taught in many computing classes. Most (all?) modern computers have numerous different processors and instruction sets, with different data types, with multiple operating systems, etc., all active in parallel.</p><p><a href="https://infosec.exchange/tags/computerarchitecture" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>computerarchitecture</span></a> <a href="https://infosec.exchange/tags/ComputerDesign" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ComputerDesign</span></a> <a href="https://infosec.exchange/tags/vulkan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>vulkan</span></a> <a href="https://infosec.exchange/tags/cuda" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>cuda</span></a> <a href="https://infosec.exchange/tags/directx" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>directx</span></a> <a href="https://infosec.exchange/tags/efi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>efi</span></a> <a href="https://infosec.exchange/tags/uefi" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>uefi</span></a> <a href="https://infosec.exchange/tags/vax" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>vax</span></a> <a href="https://infosec.exchange/tags/DigitalEquipmentCorporation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DigitalEquipmentCorporation</span></a> <a href="https://infosec.exchange/tags/openvms" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>openvms</span></a> <a href="https://infosec.exchange/tags/apple" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>apple</span></a> <a href="https://infosec.exchange/tags/applemetal" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>applemetal</span></a> <a href="https://infosec.exchange/tags/alpha" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>alpha</span></a> <a href="https://infosec.exchange/tags/itanium" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>itanium</span></a></p>
ExploreLive feeds
Mastodon is the best way to keep up with what's happening.
Follow anyone across the fediverse and see it all in chronological order. No algorithms, ads, or clickbait in sight.
Create accountLoginDrag & drop to upload