public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "vmakarov at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/37859] Bootstrap failure on mips64octeon-unknown-linux-gnu Date: Wed, 19 Nov 2008 21:27:00 -0000 [thread overview] Message-ID: <20081119212625.30482.qmail@sourceware.org> (raw) In-Reply-To: <bug-37859-4297@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from vmakarov at gcc dot gnu dot org 2008-11-19 21:26 ------- Subject: Bug 37859 Author: vmakarov Date: Wed Nov 19 21:25:00 2008 New Revision: 142018 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=142018 Log: 2008-11-19 Vladimir Makarov <vmakarov@redhat.com> PR bootstrap/37859 * ira-int.h (struct ira_loop_tree_node): New member entered_from_non_parent_p. * ira-color.c (print_loop_title): Print loop bbs. * ira-emit.c (entered_from_non_parent_p, setup_entered_from_non_parent_p): New functions. (not_modified_p): Rename to store_can_be_removed_p. Check there is no side entries. (generate_edge_moves): Use store_can_be_removed_p instead of not_modified_p. (ira_emit): Call setup_entered_from_non_parent_p. * ira-build.c (copy_info_to_removed_store_destinations): Accumulate CALL_FREQ, CALL_CROSSED_NUM, and ALLOCNO_EXCESS_PRESSURE_POINTS_NUM. (ira_flattening): Don't CHECK MEM_OPTIMIZED_DEST[_P], always update all accumulated attributes. Modified: trunk/gcc/ChangeLog trunk/gcc/ira-build.c trunk/gcc/ira-color.c trunk/gcc/ira-emit.c trunk/gcc/ira-int.h -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37859
next prev parent reply other threads:[~2008-11-19 21:27 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-10-17 2:10 [Bug bootstrap/37859] New: " nemet at gcc dot gnu dot org 2008-10-27 1:27 ` [Bug bootstrap/37859] " joefoxreal at gmail dot com 2008-11-14 3:15 ` vmakarov at redhat dot com 2008-11-19 21:27 ` vmakarov at gcc dot gnu dot org [this message] 2008-11-19 21:36 ` nemet at gcc dot gnu dot org 2008-11-20 15:58 ` hjl at gcc dot gnu dot 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=20081119212625.30482.qmail@sourceware.org \ --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: linkBe 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).