Greetings, Continued working on a complete TinyCC driven OS distribution up until one month ago, published some initial documentation at a test-site with dydns: http://tinyfront.mooo.com/docs.html
I tried to summarize the whole approach systematically, how portability towards tinycc toolchain was accomplished, and the whole philosophy of this. Maybe it's worth reading, although the reasoning behind isn't exclusive to tinycc, i586-tinycc-linux2-musl is the most relevant major test-vector for this. You'll find the download section doesn't contain the devdrop ISO yet, although i got one already which boots and runs bundled with ~500 ebuilds just fine, including dev utils such as gdb, strace, all driven by tinycc 100%. Managed to kick in with gentoo tooling on mentioned devdrop ISO self-hosting already too, tinycc compiled python.static is sufficiently complete for this, perl.static (autotools) too is, but the bash.static behaved erratically and/or segfaulted; oksh.static seems stable but is not suitable for the gentoo-specific bashism, meaning, no stable tinycc-compiled bash.static yet to keep portage self-hosting. Managed to catch a few bugs and quirks from various angles already: kernel, libc tinycc, build-system interoperability... anything but trivial, but it seems a rather practical approach to integration testing with broad test-coverage, and it's fully automated with scripting for some CI setup for the complete distro. It's hundreds of ebuilds and patches all over the place bundled into a fully forked portage tree. It seems **not** possible to re-integrate c toolchain portability back into mainstream, without going into details of this, hence the kernel fork, libc fork, portage fork, i'm left all alone with. Anyway, Linux-2.4 kernel fork with tinycc support is published for a while already: https://codeberg.org/aggi/linux-tcc Since recently i backported and tested some common asix ax7722 usb2.0 ethernet dongle, so you'll have a full tinycc-compiled somehwat POSIX99 capable kernel with ethernet available already. While ago i was too trying to keep contact with bootstrappable.org to re-integrate the complete tinycc driven distribution atop a forked dependency chain of theirs ... gladly bootstrappable.org got a tinycc system-integration path for this confirmed, so I skipped this part for the time being and focused on toolchain portability issues. All else has to wait a little, because of lacking resources and funding, and dozens of inquiries posted to various employers and three universities didn't yield anything at all for 6 month, germany 2025, as far as politics of this were concerned. Regards Michael Ackermann On 2025-08-07 08:51, [email protected] wrote: > To be debugged from nasty flaws (see messages in the list) and fully pass > conformance test suites : > > https://solidsands.com/products/supertest > > https://www.nullstone.com/htmls/ns-c.htm > > https://plumhall.com/newsite/index.html > > https://solidsands.com/a-compiler-test-suite-thats-built-for-the-job > > https://www.opengroup.org/testing/testsuites/perenial.htm > > > https://github.com/nlsandler/writing-a-c-compiler-tests > > https://github.com/c-testsuite/c-testsuite > > ... > > Otherwise you cannot rely on the compiler's output. > > Compiler optimization is another topic entirely. > > Regards. > > > ----- Mail d'origine ----- > De: Robin Rowe <[email protected]> > À: [email protected] > Envoyé: Thu, 07 Aug 2025 07:34:39 +0200 (CEST) > Objet: [Tinycc-devel] VERSION Number > > Question about version numbering... > > Version 0.9.27 was released in 2017. The current version # is 0.9.28rc. > What is needed to get TCC to version 1.0? > > Robin > > > _______________________________________________ > 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
