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 middle-end/37535] [4.4 Regression] gcc/libgcc2.c:404: internal compiler error: Floating point exception
Date: Thu, 16 Oct 2008 00:54:00 -0000 [thread overview]
Message-ID: <20081016005306.12376.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37535-276@http.gcc.gnu.org/bugzilla/>
------- Comment #19 from vmakarov at gcc dot gnu dot org 2008-10-16 00:53 -------
Subject: Bug 37535
Author: vmakarov
Date: Thu Oct 16 00:51:34 2008
New Revision: 141160
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=141160
Log:
2008-10-15 Vladimir Makarov <vmakarov@redhat.com>
PR middle-end/37535
* ira-lives.c (mark_early_clobbers): Remove.
(make_pseudo_conflict, check_and_make_def_use_conflicts,
check_and_make_def_conflicts,
make_early_clobber_and_input_conflicts,
mark_hard_reg_early_clobbers): New functions.
(process_bb_node_lives): Call
make_early_clobber_and_input_conflicts and
mark_hard_reg_early_clobbers. Make hard register inputs live
again.
* doc/rtl.texi (clobber): Change descriotion of RA behaviour for
early clobbers of pseudo-registers.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/doc/rtl.texi
trunk/gcc/ira-lives.c
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37535
prev parent reply other threads:[~2008-10-16 0:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 0:58 [Bug middle-end/37535] New: " danglin at gcc dot gnu dot org
2008-09-16 1:01 ` [Bug middle-end/37535] [4.4 Regression] " pinskia at gcc dot gnu dot org
2008-09-16 2:05 ` [Bug middle-end/37535] " danglin at gcc dot gnu dot org
2008-09-16 3:37 ` danglin at gcc dot gnu dot org
2008-09-16 3:42 ` dave at hiauly1 dot hia dot nrc dot ca
2008-09-16 13:04 ` [Bug middle-end/37535] [4.4 Regression] " rguenth at gcc dot gnu dot org
2008-09-16 16:48 ` vmakarov at redhat dot com
2008-09-17 1:11 ` vmakarov at redhat dot com
2008-09-18 12:04 ` krebbel at gcc dot gnu dot org
2008-09-19 23:26 ` vmakarov at gcc dot gnu dot org
2008-09-20 17:06 ` dave at hiauly1 dot hia dot nrc dot ca
2008-09-20 18:45 ` hjl dot tools at gmail dot com
2008-09-21 20:01 ` hjl at gcc dot gnu dot org
2008-09-22 22:47 ` hjl at gcc dot gnu dot org
2008-09-26 0:46 ` vmakarov at gcc dot gnu dot org
2008-09-30 0:39 ` hjl at gcc dot gnu dot org
2008-10-06 15:37 ` vmakarov at gcc dot gnu dot org
2008-10-11 15:12 ` danglin at gcc dot gnu dot org
2008-10-14 22:27 ` hjl at gcc dot gnu dot org
2008-10-16 0:54 ` vmakarov at gcc dot gnu dot org [this message]
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=20081016005306.12376.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).