public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joey.ye at arm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/59757] Unexpected VN_TOP in SSCVN
Date: Fri, 10 Jan 2014 13:54:00 -0000 [thread overview]
Message-ID: <bug-59757-4-mVsdlTulRH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59757-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59757
--- Comment #1 from Joey Ye <joey.ye at arm dot com> ---
foo.c: In function 'univision_ug2828gfeff01_init':
foo.c:119:1: internal compiler error: tree check: expected ssa_name, have
var_de
cl in vn_reference_compute_hash, at tree-ssa-sccvn.c:631
univision_ug2828gfeff01_init(CTL_GFX_SEP_DRIVER_t *d, int depth)
Traced to SSCVN:
Breakpoint 1, vn_reference_compute_hash (vr1=0x798fa94)
at /xxx/src/gcc/gcc/tree-ssa-sccvn.c:598
598 in /xxx/src/gcc/gcc/tree-ssa-sccvn.c
Backtrace is
vn_reference_lookup
(gdb) call debug_tree(vr1->vuse)
<var_decl 0x8fe4ba0 vn_top.15
type <void_type 0x89c08a0 void VOID
align 8 symtab 0 alias set -1 canonical type 0x89c08a0
pointer_to_this <pointer_type 0x89c0900>>
used ignored VOID file foo.c line 119 col 1
align 8>
(gdb) call debug_tree(VN_TOP)
<var_decl 0x8fe4ba0 vn_top.15
type <void_type 0x89c08a0 void VOID
align 8 symtab 0 alias set -1 canonical type 0x89c08a0
pointer_to_this <pointer_type 0x89c0900>>
used ignored VOID file foo.c line 119 col 1
align 8>
For some reason vr1->vuse is VN_TOP, which is unexpected. But I couldn't go
further without understanding SCCVN.
Anyone can help?
next prev parent reply other threads:[~2014-01-10 13:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 13:47 [Bug tree-optimization/59757] New: " joey.ye at arm dot com
2014-01-10 13:54 ` joey.ye at arm dot com [this message]
2014-01-10 14:09 ` [Bug tree-optimization/59757] " rguenth at gcc dot gnu.org
2014-01-10 16:29 ` ebotcazou at gcc dot gnu.org
2014-01-13 9:54 ` rguenth at gcc dot gnu.org
2014-01-13 11:38 ` joey.ye at arm dot com
2014-01-13 11:55 ` rguenther at suse dot de
2014-01-13 12:00 ` rguenth at gcc dot gnu.org
2014-01-20 9:14 ` joey.ye at arm 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-59757-4-mVsdlTulRH@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).