Greetings, as mentioned before compilation of QEMU with i386-tcc was desirable for: - extensive compile-time and run-time testing of TinyCC itself - cover potential use cases of and with TinyCC bootstrapping - providing an emulation host for any target ARCH other than x86_32, since TinyCC/Linux kernel was ported to x86_32 "only"
And last but not least, as a reminder, QEMU originated from Fabrice Bellard in parallel to TinyCC alike, hence there's some plausibility with the idea involved to re-integrate QEMU with i386-tcc TinyCC/OS at least. To accomplish this several qemu-versions were cross-checked against: - compatibility with TinyCC system-toolchain - Linux2.4 sysv abi (as a side effect of any portable kernel available compiled with TinyCC AND sufficient kernel ABI features to host QEMU) - and minimal dependencies Meaning this, besides TinyCC compatibility other technical aspects had to be considered. Furthermore the source bundle of qemu-0.14.1 is significantly smaller (~5MiB); instead of latest qemu-10.x (~150MiB!!!) Finally qemu-0.14.1 version (2011) is the last known suitable for re-integration with TinyCC because: - it does not rely upon __thread language extension (another exemplary case of an extension non-orthogonal to C-language) - does not rely upon python, glib2 and other excess dependencies (those do not deserve any further discussion) - probably many other yet unknown issues since i did not investigate any >=qemu-1.X..10.X further This QEMU.static 0.14.1 version is the last known to successfully compile/link with i386-tcc hence and will be included into the TinyCC/OS distribution for further runtime testing (TODO). However, qemu-0.14.1 does NOT include emulation for aarch64 and riscv64. As a consequence, if TinyCC/self-hosting compilation of QEMU was considered with acceptance-criteria for any target ARCH such as arm64-tcc, riscv64-tcc then these remain blocked indefinitely until a suitable QEMU version got re-integrated with TinyCC for these. Otherwise, of cause, GNU/gcc/llvm/clang can be utilized still and with it hundreds of millions of lines of code pulled into, to spawm a recent QEMU version,which isn't covered by a TinyCC re-integration then, among other issues. For mentioned reasons I will NOT investigate any later QEMU version nor arm64-tcc or aarch64-tcc further, besides the fact no kernel is known yet which could be ported for these with TinyCC. Feedback appreciated. Michael Ackermann On 2026-02-13 19:44, Michael Ackermann via Tinycc-devel wrote: > > I don't want to spam this list > > Actually that's no spamming at all but a highly relevant question. > > > I had no idea that the os side of this ecosystem was that far along > > It's been a three year 24/7 nonstop hackjob to make this work(tm) > for x86_32 on the OS-integration side of things, too as a BASELINE > for any other such approach. > > > riscv64g, how much legwork would it be to get going enough > > Which too raises the question if and WHO would be doing the menial > system-integration and project management tasks for it. I won't again! > As a sneak preview: it will be any kernel (and/or too uboot-loader) > remaining blocked against tinycc-toolchain support. > > Since tinycc seems in decent shape, for userspace parts there's a > good chance to get going the system integration for almost all of it > for either aarch64 and/or riscv64 with a few man-days of effort, > with a little cooperation from various people. Then again, i won't get on > board with this. > > Why that is, rather may not be discussed on tinycc-devel since it's not > them to blame, and none of my business. > > > P.S. Is there an irc or something of that nature that people are around on > > there's an abandoned #tcc channel at OFTC and libera each where i'm idling > but none dedicated to a TinyCC/Linux OS system - got no time for this. > i guess it's no problem to /join #tcc on either and ask whatever you wish, > those channels are dead silent anyway. > > and there's a few discussions at #bootstrappable at libera > > if there was any other IRC channel, then please let me know > > On 2026-02-13 19:00, tccq via Tinycc-devel wrote: > > Hi, > > > > > 2. spawning and maintaining a complete(!) TinyCC/Linux operating system > > > distribution for at least one ARCH, that is x86_32 currently which i've > > > backported and am maintaining more than 500 builds for already with > > > some > > > bootable kernel/libc and all development utilities available for > > > self-hosting > > > compilation; amazing. > > > > I had no idea that the os side of this ecosystem was that far along. A > > device without C++ is one of the ideas that drew me to this project in the > > first place. > > > > Out of curiosity, for a Raspi4B or a VisionFive 2 (riscv64g), how much > > legwork would it be to get going enough to update/bootstrap from onboard? I > > pretty much gave up using that riscv board for anything because how > > miserable the booting story was, but this would be perfect. > > > > P.S. Is there an irc or something of that nature that people are around on? > > I have a lot of small dumb questions I don't want to spam this list about. > > > > Thanks, > > TCCQ > > > > > > > > _______________________________________________ > > Tinycc-devel mailing list > > [email protected] > > https://lists.nongnu.org/mailman/listinfo/tinycc-devel
signature.asc
Description: Digital signature
_______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
