# i386 Published articles for i386. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Patches Updated To Begin Removing The Linux x32 ABI DevFeed: [Patches Updated To Begin Removing The Linux x32 ABI]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-10-08T12:09:53Z Content type: news Language: en Sources: [Phoronix]() Topics: [Linux Kernel](), [Linux]() Tags: [adoption](), [amd](), [attack-surface](), [desktop-linux](), [i386](), [intel](), [kernel](), [linux](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [lts](), [open-source-graphics](), [patches](), [phoronix](), [phoronix-test-suite](), [retirement](), [ubuntu-benchmarks](), [ubuntu-hardware](), [x86](), [x86-64]() ### AI overview Linux kernel developers have proposed patches to begin removing the x32 ABI by marking it as BROKEN. The proposal cites limited adoption and security concerns; removal would follow after this year's last LTS kernel. ### Source excerpt Linux developers are once again considering the removal of the Linux x32 ABI... ## C++26 standardizes breakpoints and debugger detection DevFeed: [C++26 standardizes breakpoints and debugger detection]() Original publisher: [Read original article]() Author: Sandor Dargo Published: 2026-09-29T22:00:00Z Content type: article Language: en Sources: [Sandor Dargo's Blog]() Topics: [c/c++](), [x86](), [gdb]() Tags: [asm](), [bare-metal](), [breakpoint](), [c-plus-plus](), [c-plus-plus-26](), [clang](), [debugger](), [debugging](), [dev](), [gcc](), [i386](), [libstdc-plus-plus](), [linux](), [x86-64]() ### AI overview C++26 adds standardized functions for triggering breakpoints and checking whether a debugger is attached. The article explains their behavior, platform-specific implementation choices, and how replaceability supports freestanding environments where operating-system debugger detection may be unavailable. ### Source excerpt If you've ever needed to hit a breakpoint programmatically in C++, you've probably written something like this: #if defined(_MSC_VER) __debugbreak(); #elif defined(__clang__) __builtin_debugtrap(); #elif defined(__GNUC__) && (defined(__i386__) || defined(__x86_64__)) __asm__ volatile("int3"); #else raise(SIGTRAP); #endif Every major C++ project reinvents this wheel. B... ## I ported Return to Castle Wolfenstein to the web with multiplayer in an hour using AI DevFeed: [I ported Return to Castle Wolfenstein to the web with multiplayer in an hour using AI]() Original publisher: [Read original article]() Author: Pieter Levels Published: 2026-06-11T00:00:00Z Content type: article Language: en Sources: [@levelsio (Pieter Levels)]() Topics: [multiplayer](), [Web]() Tags: [ai](), [cd](), [deflate](), [fable](), [filesystem](), [game](), [games](), [gpl](), [https](), [i386](), [installer](), [iso](), [multiplayer](), [native](), [networking](), [opengl](), [protocols](), [quake](), [tech](), [the-web](), [web](), [wolfenstein]() ### AI overview The author reports porting Return to Castle Wolfenstein's multiplayer mode to the web in about an hour of work, using Fable. The port started from the GPL iortcw source and adapted Emscripten patches from Wwasm, a single-player-only port; because multiplayer code differed substantially, the author manually grafted the relevant changes and fixed renderer initialization. The engine was compiled to WebAssembly with GL4ES translating OpenGL 1.x calls to WebGL2. Multiplayer networking was restored, and a matching native dedicated server was built from the same source. Game data was extracted from the 2001 CD installer, then downloaded by the browser before startup and stored in IndexedDB for reuse. The excerpt describes a working multiplayer game, including the mp_beach map. ### Source excerpt I have to stop boring all of you with my game ports but I ported another game to web with multiplayer, after Quake 1 yesterday and Quake 2 today, I thought, wh... ## Adding a new target/object backend to LLVM JITLink DevFeed: [Adding a new target/object backend to LLVM JITLink]() Original publisher: [Read original article]() Author: Kshitij Jain Published: 2023-03-28T00:00:00Z Content type: article Language: en Sources: [LLVM Project]() Topics: [LLVM](), [linker](), [JIT](), [Compiler](), [C](), [static linking](), [Assembly](), [Hardware]() Tags: [c](), [compiler](), [elf](), [hardware](), [i386](), [jit](), [jitlink](), [linker](), [linking](), [llvm](), [relocations](), [static-linking]() ### AI overview This article documents the addition of a new target/object backend to LLVM JITLink. It explains linking fundamentals, contrasts static and just-in-time linking, and describes the goal of linking 32-bit ELF objects with i386 relocations into a 32-bit process. ### Source excerpt Motivation For the last year, I have been contributing to LLVM JITLink. This post aims todoubly serve as a summary of my work and documentation for future contributors looking to add a new target/objectbackend to LLVM JITLink. We will start by establishing some background and definitions of relevant concepts. Then, we will talk about whatthe project actually entailed. Finally, we will go over the execution details of the project. The end goal of the project was to make LLVM JITLink capable of linking a 32-bit ELF object file, with i386specific relocations, into a 32-bit process on the i386 hardware architecture. If the goal of the project already makes sense to you and you are looking to get started with adding a newtarget/object backend to LLVM JITLink yourself, you can skip to the "Recap and conveniences"section. BackgroundLinking Our code often relies on external dependencies. For example, even a simple hello-world program written in C dependson the C stdlib for the printf function. These external dependencies are expressed as symbolic references, which Iwill henceforth refer to as just symbols. Symbols are names of data or functions that have unknown addresses andare resolved or fixed up during the linking process. In chronological order - The compiler converts source code to machine code. The assembler converts machine code to object files (ELF, MachO, COFF etc.) The linker links one or more object files (fixing up symbolic references along the way) and produces anexecutable or a shared library (also called shared object or dylib). For the purposes of this discussion we will focus on executables, but the points that will be made hold for sharedobjects as well. JIT linking Unlike static linking, JIT (Just-in-time) linking is performed at runtime. While a static linker producesexecutables that are stored on disk, a JIT linker produces an in-memory image of the executable - essentiallyready to execute bytes in memory. JIT linking a C program may feel very much lik ## Salsa CI now includes i386 build support DevFeed: [Salsa CI now includes i386 build support]() Original publisher: [Read original article]() Author: Salsa CI Team Published: 2020-10-09T18:20:00Z Content type: news Language: en Sources: [Bits from Debian]() Topics: [Continuous integration](), [Debian](), [builds](), [Git]() Tags: [2020](), [build](), [ci](), [continuous-integration](), [debian](), [git](), [i386](), [pipeline](), [salsa](), [tests]() ### AI overview Salsa CI, Debian's continuous integration pipeline, added support for building packages on the i386 architecture alongside amd64. The change required core pipeline updates and provides earlier feedback on package changes through automated builds and tests. ### Source excerpt Salsa CI aims at improving the Debian packaging lifecycle by delivering Continuous Integration fully compatible with Debian packaging. The main Salsa CI's project is the pipeline, that builds packages and run different tests after every git push to Salsa. The pipeline makes it possible to have a quick and early feedback about any issues the new changes may have created or solved, without the need to upload to the archive. All of the pipeline jobs run on amd64 architecture, but the Salsa CI Team has recently added support to build packages also on i386 architecture. This work started during the Salsa CI Sprint at DebConf20 after the "Where is Salsa CI right now" talk, and required different changes at the core of pipeline to make it possible. For more details, this is the related merge request: https://salsa.debian.org/salsa-ci-team/pipeline/-/merge_requests/256 If you have any questions, you can contact the Salsa CI Team at the #salsaci channel on irc.oftc.net ## LLVM Weekly - #7, Feb 17th 2014 DevFeed: [LLVM Weekly - #7, Feb 17th 2014]() Original publisher: [Read original article]() Author: Alex Bradbury Published: 2014-02-17T04:19:00Z Content type: article Language: en Sources: [LLVM Project]() Topics: [LLVM](), [Compiler](), [clang](), [Cross-Compilation](), [Embedded Systems](), [gcc](), [Rust]() Tags: [arm](), [clang](), [compilation](), [compiler](), [cross-compilation](), [embedded](), [embedded-systems](), [gcc](), [i386](), [llvm](), [llvmweekly](), [rust](), [x86-64]() ### AI overview The seventh LLVM Weekly issue reviews recent LLVM and Clang developments, including ELLCC's statically linked cross-compilation builds for several architectures, LLVM IR pointer-addressing discussions, precise garbage collection work, GCC collaboration, and control-flow integrity. ### Source excerpt Welcome to the seventh issue of LLVM Weekly, a weekly newsletter (published every Monday) covering developments in LLVM, Clang, and related projects. LLVM Weekly is brought to you by Alex Bradbury. Subscribe to future issues at http://llvmweekly.org and pass it on to anyone else you think may be interested. Please send any tips or feedback to asb@asbradbury.org, or @llvmweekly or @asbradbury on Twitter. As always, apologies if I didn't pick up your favourite mailing list discussion or commits. Do drop me a line if you think I'm missing something interesting. There haven't been that many external news stories or blog posts (that I've found) in the last week, but it's been a particularly busy week on the mailing lists with a whole bunch of interesting discussions or RFCs. The canonical home for this issue can be found here at llvmweekly.org. News and articles from around the web The ELLCC Embedded Compiler Collection now has precompiled builds available for ARM, i386, Mips, PowerPC and x86-64. Handily, these are all statically linked. The aim of ELLCC is to provide an easy to use multi-target cross compilation environment for embedded systems, and is of course based on LLVM and clang. The next Waterloo Region LLVM Social has been announced for Feb 20th. The next Paris LLVM Social will take place on Feb 24th, hosted by Mozilla. On the mailing lists Philip Reames contributed an RFC on using GetElementPtr as the canonical form for pointer addressing in LLVM IR before CodeGenPrepare. The motivation behind this proposal will be interesting to many, particularly the Rust community and other language implementors looking to target LLVM. Philip and his colleagues (at Azul Systems I believe) are looking to support precise garbage collection in LLVM, and excitingly a complete upstreamable implementation should be coming "relatively shortly. (i.e. months, not weeks, not years)" As a followup to last week's discussions on the GCC mailing list, Renato Golin has written a detailed ## Debian GNU/Hurd 2013 released! DevFeed: [Debian GNU/Hurd 2013 released!]() Original publisher: [Read original article]() Author: Ana Guerrero Published: 2013-05-22T20:50:00Z Content type: news Language: en Sources: [Bits from Debian]() Topics: [GNU/Hurd](), [Debian](), [Software](), [systems](), [Disk image]() Tags: [2013](), [announce](), [debian](), [gnu](), [gnu-hurd](), [hurd](), [i386](), [installation](), [iso](), [operating-systems](), [release](), [software](), [wheezy]() ### AI overview Debian GNU/Hurd 2013 is announced as an official GNU/Hurd port release based largely on Debian sid at the time of the Debian wheezy release. It provides installation ISOs and a pre-installed disk image for i386, with more than 10,000 available software packages. ### Source excerpt It is with huge pleasure that the Debian GNU/Hurd team announces the release of Debian GNU/Hurd 2013. This is a snapshot of Debian "sid" at the time of the Debian "wheezy" release (May 2013), so it is mostly based on the same sources. It is not an official Debian release, but it is an official Debian GNU/Hurd port release. The installation ISO images can be downloaded from Debian Ports in the usual three Debian flavors: NETINST, CD, DVD. Besides the friendly Debian installer, a pre-installed disk image is also available, making it even easier to try Debian GNU/Hurd. Debian GNU/Hurd is currently available for the i386 architecture with more than 10.000 software packages available (more than 75% of the Debian archive, and more to come!). Please make sure to read the configuration information, the FAQ, and the translator primer to get a grasp of the great features of GNU/Hurd. Due to the very small number of developers, our progress of the project has not been as fast as other successful operating systems, but we believe to have reached a very decent state, even with our limited resources. We would like to thank all the people who have worked on GNU/Hurd over the past decades. There were not many people at any given time (and still not many people today, please join!), but in the end a lot of people have contributed one way or another. Thanks everybody! This article appeared originally at GNU Hurd news and in News about Debian GNU/Hurd.