This is the mail archive of the egcs-testresults@egcs.cygnus.com mailing list for the EGCS project. See the EGCS home page for more information.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
[egcs-bugs: egcs-2.93.18 19990418 fails to compile because of a bug
in invoke.texi
> >Is it really this bad? I haven't got that far, but I do apparently get wild
> >over-writing of memory with g77-19990418, resulting in program hangs (linux)
> >or total OS hangs (W95).
Well, yes and no... My build script failed to detect a
miscompilation of g++, g77 and objc because of a failure at the end
of the bootstrap phase: That's why I got all these errors. Sorry, I
definitely have to figure out how to fix this and avoid to pollute the
list with such reports.
Actually, it might be a good idea to add an existence test directly
in the testsuite ????
Another alternative would be to create a script (compile_summary) that
automatically makes makes a report for compilation failures (to be
posted (eventually if not empty) to the egcs-bugs list with a Makefile
target as it is done for test results ???
Does this looks as a sensible idea ??
I'll try to find a way to do that if there is some interest (and
agreement on where to put it) on this topic...
[My belief is that the second approach (compile_summary script)
is better.]
On the other hand, the failure is not in the compiler, but in the
documentation. The compilation was stopped in invoke.texi compilation
(an extraneous @end table that had not been removed): but this has been
corrected while I was producing a patch :-)
--------------------------------------------------------------------
Theodore Papadopoulo
Email: Theodore.Papadopoulo@sophia.inria.fr Tel: (33) 04 92 38 76 01
--------------------------------------------------------------------