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/67027] New: [gomp4] FAIL: gfortran.dg/goacc/modules.f95 -O (internal compiler error)
Date: Mon, 27 Jul 2015 15:12:00 -0000 [thread overview]
Message-ID: <bug-67027-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67027
Bug ID: 67027
Summary: [gomp4] FAIL: gfortran.dg/goacc/modules.f95 -O
(internal compiler error)
Product: gcc
Version: 6.0
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: ---
lean-fortran/build/gcc/testsuite/gfortran1/../../gfortran
-Blean-fortran/build/gcc/testsuite/gfortran1/../../
-Blean-fortran/build/x86_64-unknown-linux-gnu/./libgfortran/
src/gcc/testsuite/gfortran.dg/goacc/modules.f95 -fno-diagnostics-show-caret
-fdiagnostics-color=never -O -fopenacc -S -o modules.s
pid is 3492 -3492
src/gcc/testsuite/gfortran.dg/goacc/modules.f95:22:0: internal compiler error:
in gimplify_adjust_omp_clauses_1, at gimp\
lify.c:6797^M
0xd4a82f gimplify_adjust_omp_clauses_1^M
src/gcc/gimplify.c:6797^M
0x1e9910a splay_tree_foreach_helper^M
src/libiberty/splay-tree.c:242^M
0x1e997a4 splay_tree_foreach^M
src/libiberty/splay-tree.c:566^M
0xd4c397 gimplify_adjust_omp_clauses^M
src/gcc/gimplify.c:7088^M
0xd507e3 gimplify_omp_workshare^M
src/gcc/gimplify.c:7888^M
0xd53ece gimplify_expr(tree_node**, gimple_statement_base**,
gimple_statement_base**, bool (*)(tree_node*), int)^M
src/gcc/gimplify.c:8932^M
0xd45e0b gimplify_stmt(tree_node**, gimple_statement_base**)^M
src/gcc/gimplify.c:5552^M
0xd36b6e gimplify_statement_list^M
src/gcc/gimplify.c:1490^M
0xd53cc4 gimplify_expr(tree_node**, gimple_statement_base**,
gimple_statement_base**, bool (*)(tree_node*), int)^M
src/gcc/gimplify.c:8865^M
0xd45e0b gimplify_stmt(tree_node**, gimple_statement_base**)^M
src/gcc/gimplify.c:5552^M
0xd3583a gimplify_bind_expr^M
src/gcc/gimplify.c:1139^M
0xd52d6e gimplify_expr(tree_node**, gimple_statement_base**,
gimple_statement_base**, bool (*)(tree_node*), int)^M
src/gcc/gimplify.c:8647^M
0xd45e0b gimplify_stmt(tree_node**, gimple_statement_base**)^M
src/gcc/gimplify.c:5552^M
0xd3389e gimplify_and_add(tree_node*, gimple_statement_base**)^M
src/gcc/gimplify.c:426^M
0xd338d6 gimplify_and_return_first^M
src/gcc/gimplify.c:438^M
0xd5060e gimplify_omp_workshare^M
src/gcc/gimplify.c:7846^M
0xd53ece gimplify_expr(tree_node**, gimple_statement_base**,
gimple_statement_base**, bool (*)(tree_node*), int)^M
src/gcc/gimplify.c:8932^M
0xd45e0b gimplify_stmt(tree_node**, gimple_statement_base**)^M
src/gcc/gimplify.c:5552^M
0xd36b6e gimplify_statement_list^M
src/gcc/gimplify.c:1490^M
0xd53cc4 gimplify_expr(tree_node**, gimple_statement_base**,
gimple_statement_base**, bool (*)(tree_node*), int)^M
src/gcc/gimplify.c:8865^M
Please submit a full bug report,^M
with preprocessed source if appropriate.^M
Please include the complete backtrace with any bug report.^M
See <http://gcc.gnu.org/bugs.html> for instructions.^M
next reply other threads:[~2015-07-27 15:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-27 15:12 vries at gcc dot gnu.org [this message]
2015-07-27 15:18 ` [Bug libgomp/67027] " vries at gcc dot gnu.org
2015-07-28 11:42 ` [Bug middle-end/67027] " nathan at gcc dot gnu.org
2015-07-28 11:43 ` nathan 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-67027-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).