public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/53411] [4.8 Regression] ICE in move_unallocated_pseudos
Date: Mon, 13 Aug 2012 11:25:00 -0000	[thread overview]
Message-ID: <bug-53411-4-PWEWxq1DO8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53411-4@http.gcc.gnu.org/bugzilla/>

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

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |vmakarov at gcc dot gnu.org

--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-08-13 11:24:31 UTC ---
ira itself also removes something, e.g. in
          rebuild_jump_labels (get_insns ());
          if (purge_all_dead_edges ())
            delete_unreachable_blocks ();
so I wouldn't move that
  if (delete_trivially_dead_insns (get_insns (), max_reg_num ()))
    df_analyze ();
too early in the function.  But perhaps it could be moved before the
  /* It is not worth to do such improvement when we use a simple
     allocation because of -O0 usage or because the function is too
     big.  */
  if (ira_conflicts_p)
    find_moveable_pseudos ();
hunk.  Vlad, what do you think?  There is still ira_flattening that tweaks the
RTL in between, dunno if it could create trivially dead insns or not.  Moving
d_t_d_i call before f_m_p call certainly fixes both of the testcases too,
haven't bootstrapped/regtested either of the patches yet.


  parent reply	other threads:[~2012-08-13 11:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-18 22:03 [Bug c/53411] New: segfault regehr at cs dot utah.edu
2012-05-20 20:04 ` [Bug middle-end/53411] [4.8 Regression] ICE in move_unallocated_pseudos pinskia at gcc dot gnu.org
2012-05-21 10:15 ` jakub at gcc dot gnu.org
2012-05-21 17:48 ` bernds at gcc dot gnu.org
2012-05-21 17:49 ` hjl.tools at gmail dot com
2012-05-25 19:18 ` bernds at gcc dot gnu.org
2012-08-13 10:55 ` jakub at gcc dot gnu.org
2012-08-13 11:07 ` bernds at gcc dot gnu.org
2012-08-13 11:25 ` jakub at gcc dot gnu.org [this message]
2012-08-14  7:43 ` jakub 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-53411-4-PWEWxq1DO8@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).