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
