public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgomp/66715] New: libgomp.oacc-c/../libgomp.oacc-c-c++-common/data-{2,3}.c exec fails -Ofast Date: Tue, 30 Jun 2015 22:38:00 -0000 [thread overview] Message-ID: <bug-66715-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66715 Bug ID: 66715 Summary: libgomp.oacc-c/../libgomp.oacc-c-c++-common/data-{2,3} .c exec fails -Ofast Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: libgomp Assignee: unassigned at gcc dot gnu.org Reporter: vries at gcc dot gnu.org CC: jakub at gcc dot gnu.org Target Milestone: --- With gomp-4_0-branch, when running target-libgomp testsuite with --target_board=unix/-Ofast, we have: c.exp: ... FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/data-2.c -DACC_DEVICE_TYPE_host_nonshm=1 -DACC_MEM_SHARED=0 execution test FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/data-3.c -DACC_DEVICE_TYPE_host_nonshm=1 -DACC_MEM_SHARED=0 execution test FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/data-2.c -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 execution test FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/data-3.c -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 execution test ... c++.exp: ... FAIL: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/data-2.c -DACC_DEVICE_TYPE_host_nonshm=1 -DACC_MEM_SHARED=0 execution test FAIL: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/data-3.c -DACC_DEVICE_TYPE_host_nonshm=1 -DACC_MEM_SHARED=0 execution test FAIL: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/data-2.c -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 execution test FAIL: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/data-3.c -DACC_DEVICE_TYPE_host=1 -DACC_MEM_SHARED=1 execution test ... failure mode: ... (gdb) up #2 0x000000000040347f in main (argc=<optimized out>, argv=<optimized out>) at src/libgomp/testsuite/libgomp.oacc-c/../libgomp.oacc-c-c++-common/data-2.c:40 40 abort (); (gdb) l 35 #pragma acc wait 36 37 for (i = 0; i < N; i++) 38 { 39 if (a[i] != 3.0) 40 abort (); 41 42 if (b[i] != 3.0) 43 abort (); 44 } ...
next reply other threads:[~2015-06-30 22:38 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-30 22:38 vries at gcc dot gnu.org [this message] 2015-06-30 22:40 ` [Bug libgomp/66715] " vries at gcc dot gnu.org 2015-07-10 15:20 ` vries at gcc dot gnu.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-66715-4@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).