public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/51990] ICE in copy_reference_ops_from_ref
Date: Wed, 25 Jan 2012 10:46:00 -0000	[thread overview]
Message-ID: <bug-51990-4-6HRlA0AY94@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51990-4@http.gcc.gnu.org/bugzilla/>

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

Richard Guenther <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2012-01-25
     Ever Confirmed|0                           |1

--- Comment #4 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-01-25 10:39:12 UTC ---
(In reply to comment #1)
> tentative fix:
> 
> Index: gcc/tree-ssa-sccvn.c
> ===================================================================
> --- gcc/tree-ssa-sccvn.c (revision 183325)
> +++ gcc/tree-ssa-sccvn.c (working copy)
> @@ -624,6 +624,10 @@ copy_reference_ops_from_ref (tree ref, V
> 
>        switch (temp.opcode)
>      {
> +    case WITH_SIZE_EXPR:
> +      temp.op0 = TREE_OPERAND (ref, 1);
> +      temp.off = 0;
> +      break;
>      case MEM_REF:
>        /* The base address gets its own vn_reference_op_s structure.  */
>        temp.op0 = TREE_OPERAND (ref, 1);
> @@ -740,6 +744,7 @@ copy_reference_ops_from_ref (tree ref, V
>        VEC_safe_push (vn_reference_op_s, heap, *result, &temp);
> 
>        if (REFERENCE_CLASS_P (ref)
> +      || TREE_CODE (ref) == WITH_SIZE_EXPR
>        || (TREE_CODE (ref) == ADDR_EXPR
>            && !is_gimple_min_invariant (ref)))
>      ref = TREE_OPERAND (ref, 0);

I think there are a lot of bugs lurking in the compiler with respect to
not handling WITH_SIZE_EXPR (which incidentially isn't a handled-component,
nor tcc_reference ...).  You btw. also need to handle re-materializing
them in create_component_ref_by_pieces_1.


  parent reply	other threads:[~2012-01-25 10:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25  8:45 [Bug tree-optimization/51990] New: " vries at gcc dot gnu.org
2012-01-25  8:55 ` [Bug tree-optimization/51990] " vries at gcc dot gnu.org
2012-01-25  9:43 ` pinskia at gcc dot gnu.org
2012-01-25 10:27 ` vries at gcc dot gnu.org
2012-01-25 10:46 ` rguenth at gcc dot gnu.org [this message]
2012-01-25 12:10 ` vries at gcc dot gnu.org
2012-01-25 12:29 ` vries at gcc dot gnu.org
2012-01-27 10:49 ` vries at gcc dot gnu.org
2012-01-27 10:51 ` vries at gcc dot gnu.org
2012-01-28 16:49 ` vries 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-51990-4-6HRlA0AY94@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).