public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Joost.VandeVondele at mat dot ethz.ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/68127] [6 Regression] ICE: error: incompatible types in PHI argument 0 / Segmentation fault
Date: Sat, 31 Oct 2015 06:38:00 -0000 [thread overview]
Message-ID: <bug-68127-4-TNjj7sORl7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-68127-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68127
Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Joost.VandeVondele at mat dot ethz
| |.ch
--- Comment #2 from Joost VandeVondele <Joost.VandeVondele at mat dot ethz.ch> ---
Interestingly, this issue is intermittent, i.e. didn't fail for two nightly
builds. Does the code generated vary if e.g. -flto=jobserver is given and
various number of tasks might be avaiable for the build ?
Meanwhile, the error message has slightly improved, not a segfault but:
cp_ddapc_util.F:201:0: error: incompatible types in PHI argument 0
RECURSIVE SUBROUTINE get_ddapc(qs_env, calc_force, density_fit_section,&
^
long int
long unsigned int
__var_6_do_683 = PHI <0(447), _637(449)>
/data/vjoost/gnu/cp2k/cp2k/makefiles/../src/cp_ddapc_util.F:201:0: error:
invalid PHI argument
__gcov0.__cp_ddapc_util_MOD_get_ddapc_I.7397_6405
/data/vjoost/gnu/cp2k/cp2k/makefiles/../src/cp_ddapc_util.F:201:0: error:
incompatible types in PHI argument 0
void
bool
.MEM_663 = PHI <__gcov0.__cp_ddapc_util_MOD_get_ddapc_I.7397_6405(447),
.MEM_554(449)>
/data/vjoost/gnu/cp2k/cp2k/makefiles/../src/cp_ddapc_util.F:201:0: internal
compiler error: verify_gimple failed
0xa4e139 verify_gimple_in_cfg(function*, bool)
../../gcc/gcc/tree-cfg.c:5082
0x93c1cc execute_function_todo
../../gcc/gcc/passes.c:1940
0x93cc43 execute_todo
../../gcc/gcc/passes.c:1995
Please submit a full bug report,
prev parent reply other threads:[~2015-10-31 6:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 7:56 [Bug middle-end/68127] New: " Joost.VandeVondele at mat dot ethz.ch
2015-10-28 8:23 ` [Bug middle-end/68127] " trippels at gcc dot gnu.org
2015-10-28 11:48 ` rguenth at gcc dot gnu.org
2015-10-31 6:38 ` Joost.VandeVondele at mat dot ethz.ch [this message]
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-68127-4-TNjj7sORl7@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).