For ttstart, I'd concentrate on testing the versions you actually ship, for the others, whoever builds them should test them and report issues to you.

I'm afraid we can't do that, unless we give up on coherency.
Remember how hard I complained about you making below-minimum testing for GCC 4.0, which broke one TICT program (crash) and pessimized three others, i.e. had a negative impact on all 4 out of 4 TICT software I tested GCC 4.0 with at first ?

For the doc tools, they're currently specific to TIGCC/*nix (and by the time we have KTIGCC on W32, we may well have a better/faster solution), so I'd rather put them somewhere into tigcc-linux.

You could also start merging the tigcc and tigcc-linux folders, by not adding more stuff to the latter. tigcc-linux has few subfolders, and will have even less when `tigcc` and `patcher` are de-duplicated (with or without integration of `patcher` into GCC)...