Bootstrapping gcc-3.0.2-branch on k6 and testresults

[Gcc testing account <caligula at cam029208 dot student dot utwente dot nl>]

Ave gcc-developers.

Since about a week gcc-3.0.2-branch  bootstraps again for my k6.
I made a bootstrap-lean,make check cycle and posted the results to the
gcc-testresults mailing list. The results were posted under the name mu.
I used a slightly enhanced gcc_build to fetch/configure/make and check
gcc.

Now I've got the following questions about this.

1) I configured gcc with host and target k6-redhat-linux-gnu.  However
  test_summary gives as native configuration i586-redhat-linux-gnu.
  When I'm doing "make check" am I really testing gcc for a k6,or am I
  testing for i586?

2)If I'm testing the right stuff (k6),do you developers find it usefull
that I'm keeping sending those results to the gcc-testresults mailing
list? There are already a lot of i586/i686 testresults.

3)If so. What's an appropiate frequency. Now I'm doing the
bootstrap/check cycle everyday. One day gcc-head,the other day gcc-3.0.x-branch.
Is posting al these results too much or is one testresults posting a week
enough?
Since the release is not far away I'm thinking about gcc-3.0.x-branch
everyday  until release and then one testresult per branch a week.


Greetings  Martijn
(please reply to the list only cause I'cant receive mail on this
account yet. I follow the list on the archives  at gcc.gnu.org)