public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/37938] New: libgomp testsuite failures on ia64-linux Date: Tue, 28 Oct 2008 14:41:00 -0000 [thread overview] Message-ID: <bug-37938-87@http.gcc.gnu.org/bugzilla/> (raw) In one bootstrap/regtest on 16way Itanium 2 I saw FAIL: libgomp.c/atomic-4.c execution test FAIL: libgomp.c/nqueens-1.c execution test FAIL: libgomp.c/pr29947-1.c execution test FAIL: libgomp.c/sort-1.c execution test FAIL: libgomp.c++/task-3.C -O3 -fomit-frame-pointer execution test FAIL: libgomp.c++/task-3.C -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions execution test FAIL: libgomp.c++/task-5.C -O1 execution test FAIL: libgomp.c++/task-5.C -O3 -g execution test in another one: FAIL: libgomp.c/nqueens-1.c execution test FAIL: libgomp.c/sort-1.c execution test FAIL: libgomp.c++/collapse-2.C -O2 execution test FAIL: libgomp.c++/task-3.C -Os execution test WARNING: program timed out. FAIL: libgomp.c++/task-5.C -O1 execution test WARNING: program timed out. FAIL: libgomp.c++/task-5.C -O2 execution test Trying atomic-4.c by hand, I see it aborts most of the time and even: extern void abort (void); int main (void) { int d = 0; int i; #pragma omp parallel for shared (d) for (i = 0; i < 100000; i++) { GOMP_atomic_start (); d = d + 1; GOMP_atomic_end (); } if (d != 100000) { __builtin_printf ("d is %d\n", d); return 1; } return 0; } fails quite often (with OMP_NUM_THREADS=16 very soon, 50% in the first invocation, with e.g. OMP_NUM_THREADS=4 less often, but still within first 40 invocations). When it fails (both for original atomic-4.c and this testcase) d is (slightly) smaller than it should be (say 1 through 10 smaller than expected), but the test never hangs. If just __sync builtin is used instead of GOMP_atomic_{start,end} pair (e.g. when double instead of long double is used in atomic-4.c, or int), then I couldn't reproduce any failures. This happens both with trunk libgomp and 4.1.2-RH system libgomp. I wonder if we need a barrier somewhere in ia64 specific code or something. GOMP_atomic_start just uses gomp_mutex_lock (&atomic_lock); and GOMP_atomic_end gomp_mutex_unlock (&atomic_lock);. I haven't seen similar problems on other arches, so I'm afraid this is ia64 specific. -- Summary: libgomp testsuite failures on ia64-linux Product: gcc Version: 4.4.0 Status: UNCONFIRMED Keywords: openmp Severity: normal Priority: P3 Component: libgomp AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: jakub at gcc dot gnu dot org GCC target triplet: ia64-linux http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37938
next reply other threads:[~2008-10-28 14:41 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-28 14:41 jakub at gcc dot gnu dot org [this message] 2008-10-28 15:04 ` [Bug libgomp/37938] " jakub at gcc dot gnu dot org 2008-10-31 20:05 ` sje at cup dot hp dot com 2008-10-31 20:16 ` jakub at gcc dot gnu dot org 2008-10-31 23:31 ` hjl dot tools at gmail dot com 2008-11-04 16:55 ` sje at cup dot hp dot com 2008-11-13 21:09 ` sje at gcc dot gnu dot org 2008-11-13 21:14 ` jakub at gcc dot gnu dot org
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-37938-87@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).