public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sje at cup dot hp dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/39631] f951 seg faults while building libgfortran
Date: Fri, 03 Apr 2009 21:19:00 -0000	[thread overview]
Message-ID: <20090403211845.6206.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39631-3107@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from sje at cup dot hp dot com  2009-04-03 21:18 -------
Putting in a workaround to fix another build problem allowed me to track this
problem down as starting with version r145309:

2009-03-30  Vladimir Makarov  <vmakarov@redhat.com>

        * reload.c (push_reload, find_dummy_reload): Use df_get_live_out
        instead of DF_LR_OUT.

        * ira-lives.c (process_bb_node_lives): Ditto.

        * ira-color.c (ira_loop_edge_freq): Use df_get_live_{out,in}
        instead of DF_LR_{OUT,IN}.

        * ira-emit.c (generate_edge_moves, add_ranges_and_copies): Ditto.

        * ira-build.c (create_bb_allocnos, create_loop_allocnos): Ditto.


-- 


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


  reply	other threads:[~2009-04-03 21:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-03 20:20 [Bug bootstrap/39631] New: " sje at cup dot hp dot com
2009-04-03 21:19 ` sje at cup dot hp dot com [this message]
2009-04-03 21:32 ` [Bug bootstrap/39631] " hjl dot tools at gmail dot com
2009-04-03 21:37 ` vmakarov at redhat dot com
2009-04-03 21:40 ` sje at cup dot hp dot com
2009-04-03 22:26 ` hjl at gcc dot gnu dot org
2009-04-12 18:44 ` danglin 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=20090403211845.6206.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: 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).