public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "uros at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/51118] [4.7 Regression] ICE: tree check: expected tree that contains ‘typed’ structure, have ‘block’ in fold_checksum_tree, at fold-const.c:14160
Date: Fri, 03 Feb 2012 07:30:00 -0000	[thread overview]
Message-ID: <bug-51118-4-X1czHaxBE2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51118-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from uros at gcc dot gnu.org 2012-02-03 07:29:41 UTC ---
Author: uros
Date: Fri Feb  3 07:29:31 2012
New Revision: 183864

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=183864
Log:
    Backport from mainline:
    2011-11-18  Uros Bizjak  <ubizjak@gmail.com>

    PR tree-optimization/51118
    * fold-const.c (fold_checksum_tree): Check for TS_TYPED structure
    before using TREE_TYPE accessor on expr.


Modified:
    branches/gcc-4_6-branch/gcc/ChangeLog
    branches/gcc-4_6-branch/gcc/fold-const.c


  parent reply	other threads:[~2012-02-03  7:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14  1:28 [Bug bootstrap/51118] New: ICE when bootstrapping on Ubuntu 11.10/amd64 with stage1 checking enabled matt at use dot net
2011-11-14 23:24 ` [Bug bootstrap/51118] " ubizjak at gmail dot com
2011-11-14 23:32 ` ubizjak at gmail dot com
2011-11-14 23:34 ` [Bug tree-optimization/51118] [4.7 Regression] ICE: tree check: expected tree that contains ‘typed’ structure, have ‘block’ in fold_checksum_tree, at fold-const.c:14160 ubizjak at gmail dot com
2011-11-17 17:34 ` ubizjak at gmail dot com
2011-11-17 18:00 ` ubizjak at gmail dot com
2011-11-18 10:00 ` ubizjak at gmail dot com
2011-11-18 10:00 ` uros at gcc dot gnu.org
2012-02-03  2:45 ` pinskia at gcc dot gnu.org
2012-02-03  7:30 ` uros at gcc dot gnu.org [this message]
2012-02-27 11:46 ` uros 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-51118-4-X1czHaxBE2@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).