public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "congh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/58521] [4.9 Regression] bootstrap failure: ICE in mem_ref_in_stmt, at tree-ssa-loop-im.c:677
Date: Thu, 26 Sep 2013 01:37:00 -0000	[thread overview]
Message-ID: <bug-58521-4-tBgILbJJVy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58521-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from congh at gcc dot gnu.org ---
Author: congh
Date: Thu Sep 26 01:36:49 2013
New Revision: 202932

URL: http://gcc.gnu.org/viewcvs?rev=202932&root=gcc&view=rev
Log:
2013-09-24  Cong Hou  <congh@google.com>

    Backport from mainline:
    2013-09-24  Richard Biener  <rguenther@suse.de>

    PR middle-end/58513
    * tree.c (reference_alias_ptr_type): Move ...
    * alias.c (reference_alias_ptr_type): ... here and implement
    in terms of the new reference_alias_ptr_type_1.
    (ref_all_alias_ptr_type_p): New helper.
    (get_deref_alias_set_1): Drop flag_strict_aliasing here,
    use ref_all_alias_ptr_type_p.
    (get_deref_alias_set): Add flag_strict_aliasing check here.
    (reference_alias_ptr_type_1): New function, split out from ...
    (get_alias_set): ... here.
    (alias_ptr_types_compatible_p): New function.
    * alias.h (reference_alias_ptr_type): Declare.
    (alias_ptr_types_compatible_p): Likewise.
    * tree.h (reference_alias_ptr_type): Remove.
    * fold-const.c (operand_equal_p): Use alias_ptr_types_compatible_p
    to compare MEM_REF alias types.

    2013-09-25  Richard Biener  <rguenther@suse.de>

    PR middle-end/58521
    * tree.c (iterative_hash_expr): Remove MEM_REF special handling.

2013-09-24  Cong Hou  <congh@google.com>

    Backport from mainline:
    2013-09-24  Richard Biener  <rguenther@suse.de>

    PR middle-end/58513
    * g++.dg/vect/pr58513.cc: New testcase.



Modified:
    branches/google/gcc-4_8/gcc/ChangeLog
    branches/google/gcc-4_8/gcc/alias.c
    branches/google/gcc-4_8/gcc/alias.h
    branches/google/gcc-4_8/gcc/fold-const.c
    branches/google/gcc-4_8/gcc/testsuite/ChangeLog
    branches/google/gcc-4_8/gcc/tree.c
    branches/google/gcc-4_8/gcc/tree.h


      parent reply	other threads:[~2013-09-26  1:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-24 18:51 [Bug bootstrap/58521] New: [4.9 Regression] bootstrap failure hjl.tools at gmail dot com
2013-09-24 19:23 ` [Bug bootstrap/58521] " dominiq at lps dot ens.fr
2013-09-25  6:39 ` glisse at gcc dot gnu.org
2013-09-25  7:15 ` [Bug bootstrap/58521] [4.9 Regression] bootstrap failure: ICE in mem_ref_in_stmt, at tree-ssa-loop-im.c:677 burnus at gcc dot gnu.org
2013-09-25  7:55 ` rguenth at gcc dot gnu.org
2013-09-25  7:59 ` schwab@linux-m68k.org
2013-09-25  8:03 ` rguenth at gcc dot gnu.org
2013-09-25  9:51 ` rguenth at gcc dot gnu.org
2013-09-25  9:52 ` rguenth at gcc dot gnu.org
2013-09-26  1:37 ` congh at gcc dot gnu.org [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-58521-4-tBgILbJJVy@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).