public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/50326] [4.7 regression] ICE in set_lattice_value, at tree-ssa-ccp.c:456
Date: Thu, 08 Sep 2011 17:42:00 -0000	[thread overview]
Message-ID: <bug-50326-4-Zi8qpUuPVb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-50326-4@http.gcc.gnu.org/bugzilla/>

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

Andreas Schwab <schwab@linux-m68k.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bernds at gcc dot gnu.org
          Component|tree-optimization           |rtl-optimization

--- Comment #1 from Andreas Schwab <schwab@linux-m68k.org> 2011-09-08 17:29:29 UTC ---
31adcf5623e6b926531c3a2973eb1b0c22d3c4c8 is the first bad commit
commit 31adcf5623e6b926531c3a2973eb1b0c22d3c4c8
Author: bernds <bernds@138bc75d-0d04-0410-961f-82ee72b054a4>
Date:   Wed Sep 7 15:57:45 2011 +0000

        * regrename.c (struct du_head): Make nregs signed.
        (closed_chains): Remove.
        (create_new_chain): Return the new chain.
        (chain_from_id): New static function.
        (dump_def_use_chain): Change argument to be an int, indicating
        the first ID to print.  All callers changed.
        (merge_overlapping_regs): Use chain_from_id.  Assert that
        chains don't conflict with themselves.
        (rename_chains): Take no argument.  Iterate over id_to_chain
        rather to find chains to rename.  Clear tick before the main
        loop.
        (struct incoming_reg_info): New struct.
        (struct bb_rename_info): New struct.
        (init_rename_info, set_incoming_from_chain, merge_chains): New
        static functions.
        (regrename_analyze): New static function, broken out of
        regrename_optimize.  Record and make use of open chain information
        at basic block boundaries, and merge chains where possible.
        (scan_rtx_reg): Make this_nregs signed.  Don't update
        closed_chains.
        (build_def_use): Return a bool to indicate success.  All callers
        changed.  Don't initialize global data here.
        (regrename_optimize): Move most code out of here into
        regrename_analyze.
        * regs.h (add_range_to_hard_reg_set, remove_range_from_hard_reg_set,
        range_overlaps_hard_reg_set_p, range_in_hard_reg_set_p): New
        static inline functions.
        * vec.h (FOR_EACH_VEC_ELT_FROM): New macro.


    git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@178645
138bc75d-0d04-0410-961f-82ee72b054a4


  parent reply	other threads:[~2011-09-08 17:30 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-08 12:41 [Bug tree-optimization/50326] New: " schwab@linux-m68k.org
2011-09-08 12:45 ` [Bug tree-optimization/50326] " schwab@linux-m68k.org
2011-09-08 17:42 ` schwab@linux-m68k.org [this message]
2011-09-09 11:36 ` [Bug rtl-optimization/50326] " bernds at gcc dot gnu.org
2011-09-09 11:45 ` rguenth at gcc dot gnu.org
2011-09-10 15:59 ` [Bug tree-optimization/50326] " schwab@linux-m68k.org
2011-09-13 13:56 ` [Bug bootstrap/50326] " jamborm at gcc dot gnu.org
2011-09-16 13:55 ` jamborm at gcc dot gnu.org
2011-09-19 19:46 ` jamborm at gcc dot gnu.org
2011-09-21 12:44 ` jamborm at gcc dot gnu.org
2011-09-27 17:36 ` rsandifo at gcc dot gnu.org
2011-09-28 12:14 ` jamborm at gcc dot gnu.org
2011-10-13 16:16 ` sje at cup dot hp.com
2011-10-18 13:04 ` mikpe at it dot uu.se
2011-10-19  8:48 ` jakub at gcc dot gnu.org
2011-10-21 13:35 ` ebotcazou 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-50326-4-Zi8qpUuPVb@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).