public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dimhen at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/59350] New: [4.9 regression] ICE: in vt_expand_var_loc_chain, at var-tracking.c:8212
Date: Fri, 29 Nov 2013 22:06:00 -0000 [thread overview]
Message-ID: <bug-59350-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59350
Bug ID: 59350
Summary: [4.9 regression] ICE: in vt_expand_var_loc_chain, at
var-tracking.c:8212
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: dimhen at gmail dot com
Fedora 19 x86_64
r205459 PASS
r205527 FAIL
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/local/gcc_current/libexec/gcc/x86_64-unknown-linux-gnu/4.9.0/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: /home/dimhen/src/gcc_current/configure
--prefix=/usr/local/gcc_current --with-multilib-list=m64
--enable-checking=yes,df,fold,rtl,tree --enable-languages=c,c++,lto
--enable-plugin --with-tune=native --with-arch=native
--enable-version-specific-runtime-libs
Thread model: posix
gcc version 4.9.0 20131129 (experimental) [trunk revision 205527] (GCC)
$ cat x.ii
struct A {
int LLVMTy;
} a;
class B;
class C {
B *Node;
int ResNo;
public:
A m_fn1() const;
void m_fn2() { m_fn1(); }
};
class D {
void *Ptr;
int IROrder;
};
class F {
public:
void m_fn1(int, D, A, C);
};
void fn1();
class B {
int NumValues;
public:
void m_fn1(int) { NumValues ? static_cast<void>(0) : fn1(); }
};
$ g++ -fpreprocessed -O1 -g -c x.ii -o x.o
x.ii: In function 'void fn2(C)':
x.ii:31:1: internal compiler error: in vt_expand_var_loc_chain, at
var-tracking.c:8212
}
^
0xf2e719 vt_expand_var_loc_chain
/home/dimhen/src/gcc_current/gcc/var-tracking.c:8212
0xf2e719 vt_expand_loc_callback
/home/dimhen/src/gcc_current/gcc/var-tracking.c:8408
0x93d7b7 cselib_expand_value_rtx_1
/home/dimhen/src/gcc_current/gcc/cselib.c:1684
0x93e6de cselib_expand_value_rtx_cb(rtx_def*, bitmap_head_def*, int, rtx_def*
(*)(rtx_def*, bitmap_head_def*, int, void*), void*)
/home/dimhen/src/gcc_current/gcc/cselib.c:1531
0xf2d9fc vt_expand_loc_callback
/home/dimhen/src/gcc_current/gcc/var-tracking.c:8344
0x93d8a9 cselib_expand_value_rtx_1
/home/dimhen/src/gcc_current/gcc/cselib.c:1649
0x93e6de cselib_expand_value_rtx_cb(rtx_def*, bitmap_head_def*, int, rtx_def*
(*)(rtx_def*, bitmap_head_def*, int, void*), void*)
/home/dimhen/src/gcc_current/gcc/cselib.c:1531
0xf2de17 vt_expand_var_loc_chain
/home/dimhen/src/gcc_current/gcc/var-tracking.c:8246
0xf2de17 vt_expand_loc_callback
/home/dimhen/src/gcc_current/gcc/var-tracking.c:8408
0x93d7b7 cselib_expand_value_rtx_1
/home/dimhen/src/gcc_current/gcc/cselib.c:1684
0x93e6de cselib_expand_value_rtx_cb(rtx_def*, bitmap_head_def*, int, rtx_def*
(*)(rtx_def*, bitmap_head_def*, int, void*), void*)
/home/dimhen/src/gcc_current/gcc/cselib.c:1531
0xf2de17 vt_expand_var_loc_chain
/home/dimhen/src/gcc_current/gcc/var-tracking.c:8246
0xf2de17 vt_expand_loc_callback
/home/dimhen/src/gcc_current/gcc/var-tracking.c:8408
0x93e6de cselib_expand_value_rtx_cb(rtx_def*, bitmap_head_def*, int, rtx_def*
(*)(rtx_def*, bitmap_head_def*, int, void*), void*)
/home/dimhen/src/gcc_current/gcc/cselib.c:1531
0xf2de17 vt_expand_var_loc_chain
/home/dimhen/src/gcc_current/gcc/var-tracking.c:8246
0xf2de17 vt_expand_loc_callback
/home/dimhen/src/gcc_current/gcc/var-tracking.c:8408
0x93d7b7 cselib_expand_value_rtx_1
/home/dimhen/src/gcc_current/gcc/cselib.c:1684
0x93e6de cselib_expand_value_rtx_cb(rtx_def*, bitmap_head_def*, int, rtx_def*
(*)(rtx_def*, bitmap_head_def*, int, void*), void*)
/home/dimhen/src/gcc_current/gcc/cselib.c:1531
0xf22658 vt_expand_var_loc_chain
/home/dimhen/src/gcc_current/gcc/var-tracking.c:8246
0xf22658 vt_expand_1pvar
/home/dimhen/src/gcc_current/gcc/var-tracking.c:8521
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
next reply other threads:[~2013-11-29 22:06 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 22:06 dimhen at gmail dot com [this message]
2013-12-02 12:45 ` [Bug middle-end/59350] " rguenth at gcc dot gnu.org
2013-12-04 14:55 ` rmansfield at qnx dot com
2013-12-05 8:16 ` dimhen at gmail dot com
2013-12-10 7:43 ` jakub at gcc dot gnu.org
2013-12-10 10:04 ` dimhen at gmail dot com
2013-12-10 11:54 ` jakub at gcc dot gnu.org
2013-12-10 13:23 ` dimhen at gmail dot com
2013-12-10 13:23 ` dimhen at gmail dot com
2013-12-10 14:27 ` rmansfield at qnx dot com
2013-12-10 17:04 ` dimhen at gmail dot com
2013-12-10 17:27 ` dimhen at gmail dot com
2013-12-13 9:03 ` ebotcazou at gcc dot gnu.org
2013-12-13 9:03 ` ebotcazou at gcc dot gnu.org
2013-12-14 11:26 ` [Bug rtl-optimization/59350] " ebotcazou at gcc dot gnu.org
2013-12-14 15:26 ` ebotcazou at gcc dot gnu.org
2013-12-14 15:27 ` ebotcazou at gcc dot gnu.org
2013-12-15 9:17 ` dimhen at gmail dot com
2013-12-15 10:36 ` ebotcazou at gcc dot gnu.org
2013-12-15 10:40 ` dimhen at gmail dot com
2013-12-15 10:47 ` dimhen at gmail dot com
2013-12-15 11:07 ` ebotcazou at gcc dot gnu.org
2013-12-15 11:10 ` dimhen at gmail dot com
2013-12-15 11:16 ` dimhen at gmail dot com
2013-12-15 12:32 ` ebotcazou at gcc dot gnu.org
2013-12-15 15:49 ` dimhen at gmail dot com
2013-12-15 19:08 ` dimhen at gmail dot com
2013-12-16 9:45 ` ktkachov at gcc dot gnu.org
2013-12-16 10:57 ` ebotcazou at gcc dot gnu.org
2013-12-16 11:42 ` ktkachov at gcc dot gnu.org
2013-12-17 13:02 ` dcb314 at hotmail dot com
2013-12-17 13:03 ` dcb314 at hotmail dot com
2013-12-17 16:03 ` ebotcazou at gcc dot gnu.org
2013-12-19 15:37 ` rguenth at gcc dot gnu.org
2013-12-19 16:12 ` dcb314 at hotmail dot com
2014-01-06 11:39 ` [Bug debug/59350] " ebotcazou at gcc dot gnu.org
2014-01-06 11:40 ` ebotcazou at gcc dot gnu.org
2014-01-06 19:45 ` dimhen at gmail dot com
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-59350-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).