https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64983
Dominique d'Humieres changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64983
--- Comment #11 from Jack Howarth ---
(In reply to Dominique d'Humieres from comment #10)
> I confirm that the dejagnu 1.5.2-3 packaging in fink restores the correct
> results.
>
> Thanks for the debugging.
Fixed in dejagnu 1.5.3.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64983
--- Comment #10 from Dominique d'Humieres ---
I confirm that the dejagnu 1.5.2-3 packaging in fink restores the correct
results.
Thanks for the debugging.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64983
--- Comment #9 from Jack Howarth ---
Note that this issue seems to only be fixable from within dejagnu and that the
commit of 6d2e2d3791bcea70131a6cf64a0a522a7b8e effectively broke the
log_summary proc in dejagnu's lib/framework.exp by reseti
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64983
Jack Howarth changed:
What|Removed |Added
CC||howarthjw at gmail dot com
--- Comment #8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64983
--- Comment #7 from howarth at bromo dot med.uc.edu ---
A regression hunt of dejagnu master revealed that the offending commit causing
this bug was...
http://git.savannah.gnu.org/cgit/dejagnu.git/commit/?id=6d2e2d3791bcea70131a6cf64a0a522a7b8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64983
--- Comment #6 from howarth at bromo dot med.uc.edu ---
This same bug has also been reported on dejagnu mailing list at...
http://lists.gnu.org/archive/html/dejagnu/2015-02/msg0.html
and claimed to be pinpointed to /usr/share/dejagnu/remote.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64983
--- Comment #5 from Iain Sandoe ---
(In reply to howarth from comment #4)
> FYI, I posted this to
> http://lists.gnu.org/archive/html/bug-dejagnu/2015-02/msg1.html and
> emailed Ben Elliston the g++.log files generated under dejagnu 1.5.1 and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64983
--- Comment #4 from howarth at bromo dot med.uc.edu ---
FYI, I posted this to
http://lists.gnu.org/archive/html/bug-dejagnu/2015-02/msg1.html and emailed
Ben Elliston the g++.log files generated under dejagnu 1.5.1 and 1.5.2.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64983
--- Comment #3 from Iain Sandoe ---
running with dejaGNU 1.6 also produces the wrong output.
I did a small amount of analysis - and it looks like the content of the
xxx.sum.sep files is not what's expected by the combiner script.
*guess* that t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64983
--- Comment #2 from howarth at bromo dot med.uc.edu ---
I am not seeing identical g++.log's being created here from dejagnu 1.5.1 and
1.5.2 on x86_64-apple-darwin14 with separate runs of...
make -k check RUNTESTFLAGS="--target_board=unix'{-m32,-m
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64983
Dominique d'Humieres changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
12 matches
Mail list logo