public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/66518] New: FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/lib-42.c -DACC_DEVICE_TYPE_host_nonshm=1 -DACC_MEM_SHARED=0 output pattern test, is , should match \[[0-9a-fA-FxX]+,256\] is not mapped
Date: Thu, 11 Jun 2015 19:10:00 -0000 [thread overview]
Message-ID: <bug-66518-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66518
Bug ID: 66518
Summary: FAIL:
libgomp.oacc-c/../libgomp.oacc-c-c++-common/lib-42.c
-DACC_DEVICE_TYPE_host_nonshm=1 -DACC_MEM_SHARED=0
output pattern test, is , should match
\[[0-9a-fA-FxX]+,256\] is not mapped
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libgomp
Assignee: unassigned at gcc dot gnu.org
Reporter: schwab@linux-m68k.org
CC: jakub at gcc dot gnu.org
Target Milestone: ---
$ gcc/xgcc -Bgcc/ ../gcc/libgomp/testsuite/libgomp.oacc-c-c++-common/lib-42.c
-Bx86_64-linux/libgomp/ -Bx86_64-linux/libgomp/.libs -Ix86_64-linux/libgomp
-I../gcc/include -I../gcc/libgomp -fopenacc -DACC_DEVICE_TYPE_host_nonshm=1
-DACC_MEM_SHARED=0 -O2 -Lx86_64-linux/libgomp/.libs -lm -o ./lib-42.exe
$ LD_LIBRARY_PATH=x86_64-linux/./libgomp/.libs:gcc: ./lib-42.exe
Segmentation fault
next reply other threads:[~2015-06-11 19:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-11 19:10 schwab@linux-m68k.org [this message]
2015-06-19 7:42 ` [Bug libgomp/66518] " tschwinge at gcc dot gnu.org
2015-10-09 15:47 ` tschwinge at gcc dot gnu.org
2015-10-26 16:24 ` tschwinge at gcc dot gnu.org
2015-10-26 16:25 ` tschwinge at gcc dot gnu.org
2015-10-26 16:35 ` tschwinge 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-66518-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: link
Be 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).