public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zadeck at naturalbridge dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/32437] [4.3 Regression] MIPS: FAIL in gcc.dg/cleanup-[8|9|10|11].c
Date: Sun, 01 Jul 2007 14:45:00 -0000 [thread overview]
Message-ID: <20070701144515.5537.qmail@sourceware.org> (raw)
In-Reply-To: <bug-32437-7151@http.gcc.gnu.org/bugzilla/>
------- Comment #24 from zadeck at naturalbridge dot com 2007-07-01 14:45 -------
Subject: Re: [4.3 Regression] MIPS: FAIL in gcc.dg/cleanup-[8|9|10|11].c
ian at airs dot com wrote:
> ------- Comment #23 from ian at airs dot com 2007-06-30 17:57 -------
> The patch in comment #19 of PR 32437 looks clearly correct. That
> patch should not be reverted, at least not by itself. I'm not clear
> on whether that was the patch that was reverted, but, if it was, I
> don't think it should have been. We are not in a time critical
> situation here. Let's take the time to figure out the right fix even
> if Richard doesn't have time to work on it.
>
> This is DCE, not DSE. In DSE we can not eliminate frame related
> instructions, because the stores into the frame are used by code which
> dataflow doesn't see: the exception unwinder. That does not apply to
> DCE. In DCE, we should be able to eliminate changes to the stack
> pointer when the stack pointer is not used, even though those changes
> are frame related.
>
> So I think this patch should be unreverted, and I don't think you should add a
> test for frame relatedness. Then we should fix PR 32475. Further comments
> over there.
>
>
>
2007-07-01 Richard Sandiford <richard@codesourcery.com>
Unreverting Richard's Revert of:
2007-06-27 Richard Sandiford <richard@codesourcery.com>
* dce.c (deletable_insn_p_1): New function, split out from...
(deletable_insn_p): ...here. Only treat bare USEs and CLOBBERs
specially, not those inside PARALLELs. Remove BODY argument
and adjust recursive call accordingly.
(prescan_insns_for_dce): Update call to delete_insn_p.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32437
next prev parent reply other threads:[~2007-07-01 14:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-20 20:04 [Bug target/32437] New: " daney at gcc dot gnu dot org
2007-06-21 9:15 ` [Bug target/32437] " daney at gcc dot gnu dot org
2007-06-21 9:30 ` rsandifo at gcc dot gnu dot org
2007-06-21 20:52 ` daney at gcc dot gnu dot org
2007-06-22 8:38 ` daney at gcc dot gnu dot org
2007-06-22 9:12 ` rsandifo at gcc dot gnu dot org
2007-06-23 1:57 ` dave at hiauly1 dot hia dot nrc dot ca
2007-06-23 2:13 ` zadeck at naturalbridge dot com
2007-06-23 15:56 ` zadeck at naturalbridge dot com
2007-06-23 16:04 ` paolo dot bonzini at lu dot unisi dot ch
2007-06-23 16:12 ` richard dot guenther at gmail dot com
2007-06-23 16:22 ` zadeck at gcc dot gnu dot org
2007-06-23 16:23 ` zadeck at naturalbridge dot com
2007-06-23 16:47 ` daney at gcc dot gnu dot org
2007-06-23 18:41 ` dave at hiauly1 dot hia dot nrc dot ca
2007-06-26 17:14 ` daney at gcc dot gnu dot org
2007-06-26 17:27 ` zadeck at naturalbridge dot com
2007-06-26 17:46 ` dave at hiauly1 dot hia dot nrc dot ca
2007-06-26 17:54 ` zadeck at naturalbridge dot com
2007-06-27 14:37 ` richard at codesourcery dot com
2007-06-27 14:39 ` zadeck at naturalbridge dot com
2007-06-30 12:26 ` richard at codesourcery dot com
2007-06-30 17:24 ` zadeck at naturalbridge dot com
2007-06-30 17:57 ` ian at airs dot com
2007-07-01 14:45 ` zadeck at naturalbridge dot com [this message]
2007-09-29 22:42 ` daney 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=20070701144515.5537.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).