--- Comment #6 from manu at gcc dot gnu dot org 2010-02-20 23:17 ---
(In reply to comment #3)
I'll be glad to make the patch, just send me the scripts that are used to read
the reports and perform breakage e-mailing and I'll ensure that my patch is
compatable.
--- Comment #7 from manu at gcc dot gnu dot org 2010-02-20 23:18 ---
Bah, Rob is not even reading mail anymore, so why bother to have this open.
No patch, no clear problem, no one is interested, so closing.
--
manu at gcc dot gnu dot org changed:
What|Removed
--- Comment #5 from rob1weld at aol dot com 2007-06-12 11:11 ---
Here is another, this caught some errors! See end of:
http://gcc.gnu.org/ml/gcc-testresults/2007-06/msg00573.html
print grep -e undefined\\ reference\\ to
/opt/gcc-4_3-build/gcc/testsuite/gcc/gcc.log | sort -u -k 2 |
--- Comment #4 from rob1weld at aol dot com 2007-06-09 03:27 ---
One enhancement I did try was adding this to the end of contrib/test_summary.
It does nothing for _me_ since I have the new assembler but for others it would
catch the failures and report them.
print ;
print ---;
--- Comment #3 from rob1weld at aol dot com 2007-05-26 18:45 ---
If it is trivial, then just prepare a patch for it, test it and send it to
gcc-patches. Opening a PR for this was a waste of electricity.
Minor and Trivial are choices on the Severity setting.
I'll be glad to make the
--- Comment #1 from pinskia at gcc dot gnu dot org 2007-05-25 07:35 ---
You know the testresults are not looked at by almost nobody (I am one of the
few person who looks at them).
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32063
--- Comment #2 from manu at gcc dot gnu dot org 2007-05-25 14:05 ---
(In reply to comment #0)
While this is trivial we should have pride in our great compiler and the
usually great results. Even if there are failures we should still present them
neatly.
If it is trivial, then just
