public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "htl10 at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/48841] [regression] lot more libgomp testsuite failures compared to 4.4.5 Date: Fri, 05 Aug 2011 23:45:00 -0000 [thread overview] Message-ID: <bug-48841-4-286eWxYFZR@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48841-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48841 Hin-Tak Leung <htl10 at users dot sourceforge.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |RESOLVED Resolution| |FIXED --- Comment #10 from Hin-Tak Leung <htl10 at users dot sourceforge.net> 2011-08-05 23:44:55 UTC --- Most strange -re-run 4.4.6 and got a different answer from previous (http://gcc.gnu.org/ml/gcc-testresults/2011-05/msg00074.html) - every part of the resulting summary file is identical, except the libgomp section. Here is the old 4.4.5, new 4.4.6, and the 4.6.1 from a few days ago: 4.4.5: === libgomp Summary === # of expected passes 2463 # of unexpected failures 9 # of unsupported tests 2 4.4.6 === libgomp Summary === # of expected passes 2511 # of unexpected failures 9 # of unsupported tests 2 4.6.1 === libgomp Summary === # of expected passes 2586 # of unsupported tests 3 These numbers make a lot more sense. The machine has not been upgraded nor used all these times, so the only two changes are (1) use of absolute path in configure, (2) during this run (in 4.6.1) I noticed /tmp was a bit small (it failed quite early on with libnumber or libiberty) so set TMIDIR to a different disk. I don't think it is the path, but it is possible I just didn't notice a not-enough temp space error; the other possibillity is some transient/intermittent error (the alignment?). Anyway, since 4.6.1 seems to work and fixes most of the regressions or what not, I am happy to let this one go.
next prev parent reply other threads:[~2011-08-05 23:45 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-05-01 22:43 [Bug libgomp/48841] New: " htl10 at users dot sourceforge.net 2011-05-01 22:56 ` [Bug libgomp/48841] " htl10 at users dot sourceforge.net 2011-05-02 10:39 ` rguenth at gcc dot gnu.org 2011-07-19 14:07 ` ro at gcc dot gnu.org 2011-08-02 11:03 ` htl10 at users dot sourceforge.net 2011-08-02 11:10 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-08-03 22:26 ` htl10 at users dot sourceforge.net 2011-08-03 23:09 ` htl10 at users dot sourceforge.net 2011-08-04 10:56 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-08-04 10:57 ` ro at CeBiTec dot Uni-Bielefeld.DE 2011-08-05 23:45 ` htl10 at users dot sourceforge.net [this message] 2011-08-09 12:18 ` ro at CeBiTec dot Uni-Bielefeld.DE
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-48841-4-286eWxYFZR@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).