public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "d.g.gorbachev at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/55525] ICE: tree check: expected array_type, have pointer_type in array_ref_low_bound, at expr.c:6768
Date: Thu, 29 Nov 2012 03:07:00 -0000	[thread overview]
Message-ID: <bug-55525-4-xtf9PH1Dyf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-55525-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55525

--- Comment #2 from Dmitry Gorbachev <d.g.gorbachev at gmail dot com> 2012-11-29 03:07:21 UTC ---
4.8.0:

In file included from :0:0:
1.c:3:6: warning: type of 's' does not match original declaration [enabled by
default]
 char s[8];
      ^
In file included from 1.c:8:0,
                 from :0:
2.c:1:7: note: previously declared here
 char *s = (char *) 0;
       ^
In file included from 1.c:8:0,
                 from :2:
1.c: In function 'main':
1.c:7:3: internal compiler error: tree check: expected array_type, have
pointer_type in array_ref_low_bound, at expr.c:6768
   return strcmp(&s[1], "foo");
   ^
0x87f7ab4 tree_check_failed(tree_node const*, char const*, int, char const*,
...)
    ../../gcc-4.8/gcc/tree.c:8955
0x815572e tree_check(tree_node*, char const*, int, char const*, tree_code)
    ../../gcc-4.8/gcc/tree.h:3680
0x82c5aec array_ref_low_bound(tree_node*)
    ../../gcc-4.8/gcc/expr.c:6768
0x82c5118 get_inner_reference(tree_node*, long long*, long long*, tree_node**,
machine_mode*, int*, int*, bool)
    ../../gcc-4.8/gcc/expr.c:6616
0x817d9d4 get_object_alignment_2
    ../../gcc-4.8/gcc/builtins.c:295
0x817e46a get_pointer_alignment_1(tree_node*, unsigned int*, unsigned long
long*)
    ../../gcc-4.8/gcc/builtins.c:493
0x817e6e0 get_pointer_alignment(tree_node*)
    ../../gcc-4.8/gcc/builtins.c:540
0x8187fd8 expand_builtin_strcmp
    ../../gcc-4.8/gcc/builtins.c:3768
0x818f7d8 expand_builtin(tree_node*, rtx_def*, rtx_def*, machine_mode, int)
    ../../gcc-4.8/gcc/builtins.c:6193
0x82d407d expand_expr_real_1(tree_node*, rtx_def*, machine_mode,
expand_modifier, rtx_def**)
    ../../gcc-4.8/gcc/expr.c:10108
0x82c96a3 expand_expr_real(tree_node*, rtx_def*, machine_mode, expand_modifier,
rtx_def**)
    ../../gcc-4.8/gcc/expr.c:7816
0x82beec7 store_expr(tree_node*, rtx_def*, int, bool)
    ../../gcc-4.8/gcc/expr.c:5192
0x82bdd8f expand_assignment(tree_node*, tree_node*, bool)
    ../../gcc-4.8/gcc/expr.c:4978
0x81d275a expand_call_stmt
    ../../gcc-4.8/gcc/cfgexpand.c:2113
0x81d2851 expand_gimple_stmt_1
    ../../gcc-4.8/gcc/cfgexpand.c:2153
0x81d2e99 expand_gimple_stmt
    ../../gcc-4.8/gcc/cfgexpand.c:2305
0x81d9a28 expand_gimple_basic_block
    ../../gcc-4.8/gcc/cfgexpand.c:4084
0x81db331 gimple_expand_cfg
    ../../gcc-4.8/gcc/cfgexpand.c:4603


  parent reply	other threads:[~2012-11-29  3:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-29  2:53 [Bug lto/55525] New: " d.g.gorbachev at gmail dot com
2012-11-29  2:55 ` [Bug lto/55525] " d.g.gorbachev at gmail dot com
2012-11-29  3:07 ` d.g.gorbachev at gmail dot com [this message]
2012-11-29  8:53 ` rguenth at gcc dot gnu.org
2012-12-05  8:48 ` rguenth at gcc dot gnu.org
2012-12-05  9:33 ` rguenth at gcc dot gnu.org
2013-01-07 14:48 ` ro at gcc dot gnu.org
2013-01-07 14:56 ` rguenther at suse dot de

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-55525-4-xtf9PH1Dyf@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).