Joseph S. Myers wrote:
One possible way of assessing activity would be to say that after 4.1 maintained CPU ports should have test results for mainline regularly sent to gcc-testresults and monitored for regressions, though this rather depends on the willingness of maintainers of embedded ports to do this testing; ports without such testing and regression monitoring could be considered at risk.Add the AVR to the list of ports that (so far) haven't had test results sent to gcc-testresults. It's only been recently that the GCC test suite has been able to run for the AVR using an outside simulator. Hopefully in the future this will change; there's a lot of work being done on the AVR port.
Only the following ports seem to have had results for 4.1.0-mainline (i.e. mainline since 4.0 branched) sent to gcc-testresults: alpha, arm, hppa, i?86/x86_64, ia64, mips, powerpc, s390, sh, sparc, although cris and mmix are evidently monitored for regressions even though they don't get test results to gcc-testresults.
I would also venture to say that the 68HC11/12 port is active as well. Though I don't know the status of testing on that port.
Eric
