Hell Robin, > What is the tcc bug reporting/ticketing system?
You can get some "tracking" there : https://savannah.nongnu.org/projects/tinycc As for the repository, it is there : https://repo.or.cz/tinycc.git > Who is our release manager? grischka is our benevolent release manager. > Is anyone working on testing tcc against that? I don't know, from some messages in the list, some are somehow verifying the RISC-V build against real world use cases. > How to get access to these commercial test suites? Request an evaluation ? Otherwise there are old and open source test suites, like : https://github.com/fujitsu/compiler-test-suite (up to date) https://github.com/UoB-HPC/TSVC_2 (10 yo) You can also "borrow" one from another compiler : https://llvm.org/docs/TestSuiteGuide.html As well as "extensions" : https://clang.llvm.org/docs/LanguageExtensions.html#c11 You have to be careful though as the standard may changes from edition to edition. There is still no official test suite released by the C++ Committee : https://isocpp.org/std/the-committee (see SG10) So right now we're at 0.9.28rc but a roadmap should be established. Reviewing the source material to create a checklist of what should be supported/tested : http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1256.pdf (C99) http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1570.pdf (C11) Imagine the future steps toward the 1.0 goal : 0.9.30 : full feature/extension review 0.9.40 : set of fixes and support to determine (spread the workload on volunteers) 0.9.50 : ... 0.9.60 0.9.70 0.9.80 0.9.90 : no more feature added, only final bug fixes 1.0.00 GOAL : full C11 support With each step having to have bug fixes and supported features upon full conformance and completion. Or maybe adhere to the Semantic Versioning : https://semver.org/ Regards. ----- Mail d'origine ----- De: Robin Rowe <[email protected]> À: [email protected] Envoyé: Fri, 08 Aug 2025 15:53:17 +0200 (CEST) Objet: Re: [Tinycc-devel] VERSION Number 1.0 David wrote: > To be debugged from nasty flaws (see messages in the list) What is the tcc bug reporting/ticketing system? Is there a QA and bug management policy document? Who is our release manager? Who assigns version numbers? David wrote: > and fully pass conformance test suites : The tests for writing-a-c-compiler-tests are online. Seem a good place to start. Is anyone working on testing tcc against that? David, the list of C test suites you shared looks great, appreciate you. However, many are pay-to-play products. How to get access to these commercial test suites? Michael wrote: > 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 Testing tcc by having a distro entirely built by tcc. That is clever. Very nice. Robin _______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel _______________________________________________ Tinycc-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/tinycc-devel
