MastodonTech.de

mage_of_dragonsFedi Osdevs, please I need I to know: Why is the physical address in real mode segmentreg * 16 + offset?? Where does the 16 come from?<a href="https://mastodon.social/tags/osdev" class="mention hashtag" rel="nofollow noopener" target="_blank">#osdev</a> <a href="https://mastodon.social/tags/programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#programming</a> <a href="https://mastodon.social/tags/askfedi" class="mention hashtag" rel="nofollow noopener" target="_blank">#askfedi</a> <a href="https://mastodon.social/tags/x86" class="mention hashtag" rel="nofollow noopener" target="_blank">#x86</a> <a href="https://mastodon.social/tags/cpu" class="mention hashtag" rel="nofollow noopener" target="_blank">#cpu</a>

Paolo AmorosoAsm Editor is a web app IDE for learning, developing, and running x86, M68K, RISC-V, and MIPS Assembly code. It features an editor, assembler, and debugger, as well as other tools and learning resources.<a href="https://asm-editor.specy.app" rel="nofollow noopener" translate="no" target="_blank">https://asm-editor.specy.app</a><a href="https://github.com/Specy/asm-editor" rel="nofollow noopener" translate="no" target="_blank">https://github.com/Specy/asm-editor</a><a href="https://oldbytes.space/tags/x86" class="mention hashtag" rel="nofollow noopener" target="_blank">#x86</a> <a href="https://oldbytes.space/tags/m68k" class="mention hashtag" rel="nofollow noopener" target="_blank">#m68k</a> <a href="https://oldbytes.space/tags/mips" class="mention hashtag" rel="nofollow noopener" target="_blank">#mips</a> <a href="https://oldbytes.space/tags/assembly" class="mention hashtag" rel="nofollow noopener" target="_blank">#assembly</a> <a href="https://oldbytes.space/tags/riscv" class="mention hashtag" rel="nofollow noopener" target="_blank">#riscv</a>

Hacker NewsLet's Learn x86-64 Assembly Part 0 – Setup and First Steps<a href="https://gpfault.net/posts/asm-tut-0.txt.html" rel="nofollow noopener" translate="no" target="_blank">https://gpfault.net/posts/asm-tut-0.txt.html</a><a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/Learn" class="mention hashtag" rel="nofollow noopener" target="_blank">#Learn</a> <a href="https://mastodon.social/tags/x86" class="mention hashtag" rel="nofollow noopener" target="_blank">#x86</a>-64 <a href="https://mastodon.social/tags/Assembly" class="mention hashtag" rel="nofollow noopener" target="_blank">#Assembly</a> <a href="https://mastodon.social/tags/Part" class="mention hashtag" rel="nofollow noopener" target="_blank">#Part</a> #0 #– <a href="https://mastodon.social/tags/Setup" class="mention hashtag" rel="nofollow noopener" target="_blank">#Setup</a> <a href="https://mastodon.social/tags/and" class="mention hashtag" rel="nofollow noopener" target="_blank">#and</a> <a href="https://mastodon.social/tags/First" class="mention hashtag" rel="nofollow noopener" target="_blank">#First</a> <a href="https://mastodon.social/tags/Steps" class="mention hashtag" rel="nofollow noopener" target="_blank">#Steps</a> <a href="https://mastodon.social/tags/x86_64" class="mention hashtag" rel="nofollow noopener" target="_blank">#x86_64</a> <a href="https://mastodon.social/tags/Assembly" class="mention hashtag" rel="nofollow noopener" target="_blank">#Assembly</a> <a href="https://mastodon.social/tags/Learning" class="mention hashtag" rel="nofollow noopener" target="_blank">#Learning</a> <a href="https://mastodon.social/tags/Programming" class="mention hashtag" rel="nofollow noopener" target="_blank">#Programming</a> <a href="https://mastodon.social/tags/Tutorials" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tutorials</a> <a href="https://mastodon.social/tags/Tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tech</a> <a href="https://mastodon.social/tags/Education" class="mention hashtag" rel="nofollow noopener" target="_blank">#Education</a>

C:\KKJ\>:idle:I'm in a middle of (memory management) refactor. Here is the updated main menu.<a href="https://fosstodon.org/tags/GameDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#GameDev</a> <a href="https://fosstodon.org/tags/x86" class="mention hashtag" rel="nofollow noopener" target="_blank">#x86</a> <a href="https://fosstodon.org/tags/Assembly" class="mention hashtag" rel="nofollow noopener" target="_blank">#Assembly</a> <a href="https://fosstodon.org/tags/BareMetal" class="mention hashtag" rel="nofollow noopener" target="_blank">#BareMetal</a> <a href="https://fosstodon.org/tags/PixelArt" class="mention hashtag" rel="nofollow noopener" target="_blank">#PixelArt</a>

Blake PattersonDid you know that the 'NT' in Windows NT stood for "Nine Ten"? The intended core platform for the OS was the then-expected Intel i910 RISC processor, which was to be the rebranded moniker for the i860 that can be found in the wild. *It never came to be due to the i860s terrible handling of context switching -- a capability that a CPU for a multitasking, multiuser workstation OS must be able to do _very_efficiently_. The i860 wasn't. <a href="https://www.youtube.com/watch?v=WTkFGZqVCM8&t=459s" rel="nofollow noopener" translate="no" target="_blank">https://www.youtube.com/watch?v=WTkFGZqVCM8&t=459s</a>*** EDIT: Several have pointed to sources indicating differently that NT stood for N10, which was the codename for the i860, so -- N10, N-Ten > NT. <a href="https://oldbytes.space/tags/TIL" class="mention hashtag" rel="nofollow noopener" target="_blank">#TIL</a> <a href="https://oldbytes.space/tags/WindowsNT" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowsNT</a> <a href="https://oldbytes.space/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> <a href="https://oldbytes.space/tags/Intel" class="mention hashtag" rel="nofollow noopener" target="_blank">#Intel</a> <a href="https://oldbytes.space/tags/i860" class="mention hashtag" rel="nofollow noopener" target="_blank">#i860</a> <a href="https://oldbytes.space/tags/i910" class="mention hashtag" rel="nofollow noopener" target="_blank">#i910</a> <a href="https://oldbytes.space/tags/vintagecomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#vintagecomputing</a> <a href="https://oldbytes.space/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrocomputing</a> <a href="https://oldbytes.space/tags/OS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OS</a> <a href="https://oldbytes.space/tags/techhistory" class="mention hashtag" rel="nofollow noopener" target="_blank">#techhistory</a> <a href="https://oldbytes.space/tags/RISC" class="mention hashtag" rel="nofollow noopener" target="_blank">#RISC</a> <a href="https://oldbytes.space/tags/x86" class="mention hashtag" rel="nofollow noopener" target="_blank">#x86</a> <a href="https://oldbytes.space/tags/processors" class="mention hashtag" rel="nofollow noopener" target="_blank">#processors</a> <a href="https://oldbytes.space/tags/computers" class="mention hashtag" rel="nofollow noopener" target="_blank">#computers</a> <a href="https://oldbytes.space/tags/computinghistory" class="mention hashtag" rel="nofollow noopener" target="_blank">#computinghistory</a> <a href="https://oldbytes.space/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Microsoft</a>

Blake PattersonI just stumbled upon this upgrade I would have leapt at a few years back when I was building up my "new" Tandy 1000HX: Tandy 1000 EX/HX 3-in-1 V2 Adapter --- 640K RAM + 2x Serial + Parallel + XTIDE Upgrade by Rob Krenicki<a href="https://www.ebay.com/itm/197473626636" rel="nofollow noopener" translate="no" target="_blank">https://www.ebay.com/itm/197473626636</a>It looks like the creator of this device, who posted the project to GitHub, has made his last production run, sadly. Several are available still on eBay. It doesn't look like the RAM expansion has the DMA chip, but that really doesn't much matter. What a great unit. I upgraded my own 1000HX to this spec -- but did it the Hard way (note the capital H). <a href="https://github.com/rkrenicki/Tandy-EX-HX-3in1" rel="nofollow noopener" translate="no" target="_blank">https://github.com/rkrenicki/Tandy-EX-HX-3in1</a><a href="https://oldbytes.space/tags/Tandy" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tandy</a> <a href="https://oldbytes.space/tags/Tandy1000" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tandy1000</a> <a href="https://oldbytes.space/tags/Tandy1000HX" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tandy1000HX</a> <a href="https://oldbytes.space/tags/Tandy1000EX" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tandy1000EX</a> <a href="https://oldbytes.space/tags/vintagecomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#vintagecomputing</a> <a href="https://oldbytes.space/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrocomputing</a> <a href="https://oldbytes.space/tags/retrogaming" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrogaming</a> <a href="https://oldbytes.space/tags/XTIDE" class="mention hashtag" rel="nofollow noopener" target="_blank">#XTIDE</a> <a href="https://oldbytes.space/tags/modernretro" class="mention hashtag" rel="nofollow noopener" target="_blank">#modernretro</a> <a href="https://oldbytes.space/tags/eBay" class="mention hashtag" rel="nofollow noopener" target="_blank">#eBay</a> <a href="https://oldbytes.space/tags/x86" class="mention hashtag" rel="nofollow noopener" target="_blank">#x86</a> <a href="https://oldbytes.space/tags/TRS80" class="mention hashtag" rel="nofollow noopener" target="_blank">#TRS80</a> <a href="https://oldbytes.space/tags/RadioShack" class="mention hashtag" rel="nofollow noopener" target="_blank">#RadioShack</a>

🧿🪬🍄🌈🎮💻🚲🥓🎃💀🏴🛻🇺🇸I suppose the <a href="https://mastodon.social/tags/Nvidia" class="mention hashtag" rel="nofollow noopener" target="_blank">#Nvidia</a> <a href="https://mastodon.social/tags/Jetson" class="mention hashtag" rel="nofollow noopener" target="_blank">#Jetson</a> form factor is a kind of standard interface for <a href="https://mastodon.social/tags/systemOnModule" class="mention hashtag" rel="nofollow noopener" target="_blank">#systemOnModule</a> <a href="https://mastodon.social/tags/SBC" class="mention hashtag" rel="nofollow noopener" target="_blank">#SBC</a> There's already a <a href="https://mastodon.social/tags/RiscV" class="mention hashtag" rel="nofollow noopener" target="_blank">#RiscV</a> <a href="https://mastodon.social/tags/SoM" class="mention hashtag" rel="nofollow noopener" target="_blank">#SoM</a> called the <a href="https://mastodon.social/tags/MilkV" class="mention hashtag" rel="nofollow noopener" target="_blank">#MilkV</a> Jupiter that's supposedly compatible with a <a href="https://mastodon.social/tags/NvidiaJetson" class="mention hashtag" rel="nofollow noopener" target="_blank">#NvidiaJetson</a> <a href="https://mastodon.social/tags/carrierBoard" class="mention hashtag" rel="nofollow noopener" target="_blank">#carrierBoard</a>, and now the <a href="https://mastodon.social/tags/radxaN150" class="mention hashtag" rel="nofollow noopener" target="_blank">#radxaN150</a> with an <a href="https://mastodon.social/tags/x86" class="mention hashtag" rel="nofollow noopener" target="_blank">#x86</a> chip.I'd be interested in seeing someone try various Jetson boards with the available modules.<a href="https://mastodon.social/@schizanon/114683291238623615" rel="nofollow noopener" translate="no" target="_blank">https://mastodon.social/@schizanon/114683291238623615</a>

.:\dGh/:.Can you make your own Fedora distro with only 32-bit libs?And see what doesn't works, or even if it boots at all?<a href="https://mastodon.social/tags/Fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fedora</a> <a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://mastodon.social/tags/x86" class="mention hashtag" rel="nofollow noopener" target="_blank">#x86</a> <a href="https://mastodon.social/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#FOSS</a> <a href="https://mastodon.social/tags/OSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#OSS</a> <a href="https://mastodon.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenSource</a>

Deutschland<a href="https://www.europesays.com/de/219053/" rel="nofollow noopener" translate="no" target="_blank">https://www.europesays.com/de/219053/</a> Aus für Rosetta 2 bei Apple: Entwickler sollen Kompatibilität mit M-Macs prüfen <a href="https://pubeurope.com/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apple</a> <a href="https://pubeurope.com/tags/AppleSilicon" class="mention hashtag" rel="nofollow noopener" target="_blank">#AppleSilicon</a> <a href="https://pubeurope.com/tags/Deutschland" class="mention hashtag" rel="nofollow noopener" target="_blank">#Deutschland</a> <a href="https://pubeurope.com/tags/Germany" class="mention hashtag" rel="nofollow noopener" target="_blank">#Germany</a> <a href="https://pubeurope.com/tags/Intel" class="mention hashtag" rel="nofollow noopener" target="_blank">#Intel</a> <a href="https://pubeurope.com/tags/IT" class="mention hashtag" rel="nofollow noopener" target="_blank">#IT</a> <a href="https://pubeurope.com/tags/Kompatibilit%C3%A4t" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kompatibilität</a> <a href="https://pubeurope.com/tags/Mac" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mac</a> <a href="https://pubeurope.com/tags/macOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#macOS</a> <a href="https://pubeurope.com/tags/Science" class="mention hashtag" rel="nofollow noopener" target="_blank">#Science</a> <a href="https://pubeurope.com/tags/Science" class="mention hashtag" rel="nofollow noopener" target="_blank">#Science</a>&Technology <a href="https://pubeurope.com/tags/Technik" class="mention hashtag" rel="nofollow noopener" target="_blank">#Technik</a> <a href="https://pubeurope.com/tags/Technology" class="mention hashtag" rel="nofollow noopener" target="_blank">#Technology</a> <a href="https://pubeurope.com/tags/Wissenschaft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wissenschaft</a> <a href="https://pubeurope.com/tags/Wissenschaft" class="mention hashtag" rel="nofollow noopener" target="_blank">#Wissenschaft</a>&Technik <a href="https://pubeurope.com/tags/x86" class="mention hashtag" rel="nofollow noopener" target="_blank">#x86</a>

Gábor SAMUThis week in computing history - On June 26, 1990, <a href="https://mstdn.ca/tags/IBM" class="mention hashtag" rel="nofollow noopener" target="_blank">#IBM</a> launched the Personal System/1 (PS/1) <a href="https://americanhistory.si.edu/collections/object/nmah_1303225" rel="nofollow noopener" translate="no" target="_blank">https://americanhistory.si.edu/collections/object/nmah_1303225</a> <a href="https://mstdn.ca/tags/x86" class="mention hashtag" rel="nofollow noopener" target="_blank">#x86</a> <a href="https://mstdn.ca/tags/Intel80286" class="mention hashtag" rel="nofollow noopener" target="_blank">#Intel80286</a>

Hacker NewsWindows x86-64 System Call Table (XP/2003/Vista/7/8/10/11 and Server)<a href="https://j00ru.vexillium.org/syscalls/nt/64/" rel="nofollow noopener" translate="no" target="_blank">https://j00ru.vexillium.org/syscalls/nt/64/</a><a href="https://mastodon.social/tags/HackerNews" class="mention hashtag" rel="nofollow noopener" target="_blank">#HackerNews</a> <a href="https://mastodon.social/tags/Windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> <a href="https://mastodon.social/tags/System" class="mention hashtag" rel="nofollow noopener" target="_blank">#System</a> <a href="https://mastodon.social/tags/Calls" class="mention hashtag" rel="nofollow noopener" target="_blank">#Calls</a> <a href="https://mastodon.social/tags/x86" class="mention hashtag" rel="nofollow noopener" target="_blank">#x86</a>-64 <a href="https://mastodon.social/tags/WindowsXP" class="mention hashtag" rel="nofollow noopener" target="_blank">#WindowsXP</a> <a href="https://mastodon.social/tags/Windows10" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows10</a> <a href="https://mastodon.social/tags/TechResearch" class="mention hashtag" rel="nofollow noopener" target="_blank">#TechResearch</a> <a href="https://mastodon.social/tags/Syscalls" class="mention hashtag" rel="nofollow noopener" target="_blank">#Syscalls</a>

C:\KKJ\>:idle:Coding assembly in the wild. <a href="https://fosstodon.org/tags/x86" class="mention hashtag" rel="nofollow noopener" target="_blank">#x86</a> <a href="https://fosstodon.org/tags/Assembly" class="mention hashtag" rel="nofollow noopener" target="_blank">#Assembly</a> <a href="https://fosstodon.org/tags/GaneDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#GaneDev</a> <a href="https://fosstodon.org/tags/Thinkpad" class="mention hashtag" rel="nofollow noopener" target="_blank">#Thinkpad</a>

Paolo Amoroso☝️ <a href="https://oldbytes.space/@bitsavers" class="u-url mention" rel="nofollow noopener" target="_blank">@bitsavers</a> has just posted yet another computing history treasure: the scans of the original Digital Research listings of the sources of CP/M 2.2, CP/M Plus 3.0, CP/M-86, and Concurrent CP/M-86 in Intel 8080 Assembly, PL/M, and Intel 8086 Assembly.<a href="http://www.bitsavers.org/pdf/digitalResearch/CPM_Listings/" rel="nofollow noopener" translate="no" target="_blank">http://www.bitsavers.org/pdf/digitalResearch/CPM_Listings/</a><a href="https://oldbytes.space/tags/retrocomputing" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrocomputing</a> <a href="https://oldbytes.space/tags/cpm" class="mention hashtag" rel="nofollow noopener" target="_blank">#cpm</a> <a href="https://oldbytes.space/tags/intel8080" class="mention hashtag" rel="nofollow noopener" target="_blank">#intel8080</a> <a href="https://oldbytes.space/tags/x86" class="mention hashtag" rel="nofollow noopener" target="_blank">#x86</a>

C:\KKJ\>:idle:Latest (very rough) version of the game is ready to test via browser (jsDOS).=> <a href="https://smol.p1x.in/assembly/game12/game12.html" rel="nofollow noopener" translate="no" target="_blank">https://smol.p1x.in/assembly/game12/game12.html</a>There is a placeholder tune, beware if you're using headphones ;)F1- panning F2- constructing rails F3- switches F4- not implemented yetWORK-IN-PROGRESSCurrent size (with that awful music): 6.8 KiB (6,972)<a href="https://fosstodon.org/tags/Assembly" class="mention hashtag" rel="nofollow noopener" target="_blank">#Assembly</a> <a href="https://fosstodon.org/tags/x86" class="mention hashtag" rel="nofollow noopener" target="_blank">#x86</a> <a href="https://fosstodon.org/tags/BareMetal" class="mention hashtag" rel="nofollow noopener" target="_blank">#BareMetal</a> <a href="https://fosstodon.org/tags/GameDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#GameDev</a> <a href="https://fosstodon.org/tags/IndieDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#IndieDev</a> <a href="https://fosstodon.org/tags/PixelArt" class="mention hashtag" rel="nofollow noopener" target="_blank">#PixelArt</a> <a href="https://fosstodon.org/tags/MSDOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#MSDOS</a>

.:\dGh/:.Goodbye Hackintosh 2006 - 2026First release: Mac OS 10.4.4 by Maxxus (x86, PPC, PPC64) Last release: macOS 26 Tahoe by Apple (x86, ARM64)<a href="https://www.macrumors.com/2025/06/09/intel-macs-no-more-updates/" rel="nofollow noopener" translate="no" target="_blank">https://www.macrumors.com/2025/06/09/intel-macs-no-more-updates/</a><a href="https://mastodon.social/tags/Apple" class="mention hashtag" rel="nofollow noopener" target="_blank">#Apple</a> <a href="https://mastodon.social/tags/macOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#macOS</a> <a href="https://mastodon.social/tags/Mac" class="mention hashtag" rel="nofollow noopener" target="_blank">#Mac</a> <a href="https://mastodon.social/tags/MacBook" class="mention hashtag" rel="nofollow noopener" target="_blank">#MacBook</a> <a href="https://mastodon.social/tags/iMac" class="mention hashtag" rel="nofollow noopener" target="_blank">#iMac</a> <a href="https://mastodon.social/tags/MacBookAir" class="mention hashtag" rel="nofollow noopener" target="_blank">#MacBookAir</a> <a href="https://mastodon.social/tags/MacBookPro" class="mention hashtag" rel="nofollow noopener" target="_blank">#MacBookPro</a> <a href="https://mastodon.social/tags/WWDC" class="mention hashtag" rel="nofollow noopener" target="_blank">#WWDC</a> <a href="https://mastodon.social/tags/WWDC25" class="mention hashtag" rel="nofollow noopener" target="_blank">#WWDC25</a> <a href="https://mastodon.social/tags/MacStudio" class="mention hashtag" rel="nofollow noopener" target="_blank">#MacStudio</a> <a href="https://mastodon.social/tags/MacMini" class="mention hashtag" rel="nofollow noopener" target="_blank">#MacMini</a> <a href="https://mastodon.social/tags/macOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#macOS</a> <a href="https://mastodon.social/tags/macOS26" class="mention hashtag" rel="nofollow noopener" target="_blank">#macOS26</a> <a href="https://mastodon.social/tags/macOSTahoe" class="mention hashtag" rel="nofollow noopener" target="_blank">#macOSTahoe</a> <a href="https://mastodon.social/tags/Tahoe" class="mention hashtag" rel="nofollow noopener" target="_blank">#Tahoe</a> <a href="https://mastodon.social/tags/Hackintosh" class="mention hashtag" rel="nofollow noopener" target="_blank">#Hackintosh</a> <a href="https://mastodon.social/tags/x86" class="mention hashtag" rel="nofollow noopener" target="_blank">#x86</a> <a href="https://mastodon.social/tags/Intel" class="mention hashtag" rel="nofollow noopener" target="_blank">#Intel</a> <a href="https://mastodon.social/tags/Hardware" class="mention hashtag" rel="nofollow noopener" target="_blank">#Hardware</a> <a href="https://mastodon.social/tags/PC" class="mention hashtag" rel="nofollow noopener" target="_blank">#PC</a> <a href="https://mastodon.social/tags/PCHardware" class="mention hashtag" rel="nofollow noopener" target="_blank">#PCHardware</a> <a href="https://mastodon.social/tags/Computer" class="mention hashtag" rel="nofollow noopener" target="_blank">#Computer</a> <a href="https://mastodon.social/tags/Computers" class="mention hashtag" rel="nofollow noopener" target="_blank">#Computers</a> <a href="https://mastodon.social/tags/Laptop" class="mention hashtag" rel="nofollow noopener" target="_blank">#Laptop</a> <a href="https://mastodon.social/tags/Laptops" class="mention hashtag" rel="nofollow noopener" target="_blank">#Laptops</a>

Paolo AmorosoJimmy Miller posted a short introduction to the basics of reading machine code. He focuses on the actual raw machine code, not Assembly, of aarch64 and x86-64.<a href="https://jimmyhmiller.com/machine-code-isnt-scary" rel="nofollow noopener" translate="no" target="_blank">https://jimmyhmiller.com/machine-code-isnt-scary</a><a href="https://oldbytes.space/tags/assembly" class="mention hashtag" rel="nofollow noopener" target="_blank">#assembly</a> <a href="https://oldbytes.space/tags/arm64" class="mention hashtag" rel="nofollow noopener" target="_blank">#arm64</a> <a href="https://oldbytes.space/tags/x86" class="mention hashtag" rel="nofollow noopener" target="_blank">#x86</a>

C:\KKJ\>:idle:Back-end for supporting rails switches is almost done.<a href="https://fosstodon.org/tags/Assembly" class="mention hashtag" rel="nofollow noopener" target="_blank">#Assembly</a> <a href="https://fosstodon.org/tags/x86" class="mention hashtag" rel="nofollow noopener" target="_blank">#x86</a>

C:\KKJ\>:idle:I'm back to my "main" game development. Using knowledge gain in the OS development I'm refactoring the code. New sprites are loading!<a href="https://fosstodon.org/tags/GameDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#GameDev</a> <a href="https://fosstodon.org/tags/IndieGameDev" class="mention hashtag" rel="nofollow noopener" target="_blank">#IndieGameDev</a> <a href="https://fosstodon.org/tags/Assembly" class="mention hashtag" rel="nofollow noopener" target="_blank">#Assembly</a> <a href="https://fosstodon.org/tags/x86" class="mention hashtag" rel="nofollow noopener" target="_blank">#x86</a> <a href="https://fosstodon.org/tags/MSDOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#MSDOS</a>

Felix Palmen :freebsd: :c64:I recently took a dive into <a href="https://mastodon.bsd.cafe/tags/C11" class="mention hashtag" rel="nofollow noopener" target="_blank">#C11</a> <a href="https://mastodon.bsd.cafe/tags/atomics" class="mention hashtag" rel="nofollow noopener" target="_blank">#atomics</a> to come up with alternative queue implementations not requiring locking some <a href="https://mastodon.bsd.cafe/tags/mutex" class="mention hashtag" rel="nofollow noopener" target="_blank">#mutex</a>.TBH, I have a hard time understanding the <a href="https://mastodon.bsd.cafe/tags/memory" class="mention hashtag" rel="nofollow noopener" target="_blank">#memory</a> <a href="https://mastodon.bsd.cafe/tags/ordering" class="mention hashtag" rel="nofollow noopener" target="_blank">#ordering</a> constraints defined by C11. I mean, I code <a href="https://mastodon.bsd.cafe/tags/assembler" class="mention hashtag" rel="nofollow noopener" target="_blank">#assembler</a> on a <a href="https://mastodon.bsd.cafe/tags/mos6502" class="mention hashtag" rel="nofollow noopener" target="_blank">#mos6502</a> (for the <a href="https://mastodon.bsd.cafe/tags/c64" class="mention hashtag" rel="nofollow noopener" target="_blank">#c64</a>), so caches, pipelines and all that modern crap is kind of alien rocket science anyways 😆.But seriously, they try to abstract from what the hardware provides (different kinds of memory barrier instructions, IMHO somewhat easier to understand), so the compiler can pick the appropriate one depending on the target CPU. But wrapping your head around their definition really hurts the brain 🙈.Yesterday, I found a source telling me that <a href="https://mastodon.bsd.cafe/tags/amd64" class="mention hashtag" rel="nofollow noopener" target="_blank">#amd64</a> (or <a href="https://mastodon.bsd.cafe/tags/x86" class="mention hashtag" rel="nofollow noopener" target="_blank">#x86</a> in general?) always has strong ordering for reads, so no matter which oderding constraint you put in your atomic_load and friends, the compiler will generate the same code and it will work. Oh boy, how should I ever verify my code works on e.g. aarch64 without owning such hardware?

Eduardo Medina 🇪🇸Para mí los mejores procesadores <a href="https://mastodon.social/tags/x86" class="mention hashtag" rel="nofollow noopener" target="_blank">#x86</a> de la historia son los <a href="https://mastodon.social/tags/Intel" class="mention hashtag" rel="nofollow noopener" target="_blank">#Intel</a> Core 2 Quad. No sé cómo estarán ahora, pero puedo asegurar que en 2017, prácticamente 10 años después de su lanzamiento, seguían siendo productos bastante competitivos para muchos ámbitos, si bien hay que reconocer que no servían de mucho con videojuegos triple A de última generación de la época.<a href="https://mastodon.social/tags/IntelCore" class="mention hashtag" rel="nofollow noopener" target="_blank">#IntelCore</a>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#x86