From: Jeff Law <law@redhat.com>
To: Segher Boessenkool <segher@kernel.crashing.org>, gcc-patches@gcc.gnu.org
Cc: dje.gcc@gmail.com
Subject: Re: [PATCH 2/5] dce: Don't dead-code delete separately wrapped restores
Date: Mon, 26 Sep 2016 16:55:00 -0000 [thread overview]
Message-ID: <dd86bb38-bd12-ecc6-d3cc-baf0d0aa8856@redhat.com> (raw)
In-Reply-To: <e8a1ae7870bbbd8d70d55483b24e014d0c4713fe.1474616087.git.segher@kernel.crashing.org>
On 09/23/2016 02:21 AM, Segher Boessenkool wrote:
> If there is a separately wrapped register restore on some path that
> is dead (say, control goes into an endless loop after it), then we
> cannot delete that restore because that would confuse the DWARF CFI
> (if there is another path joining after this).
> This happens with gcc.dg/torture/pr53168.c, for example.
>
>
> 2016-09-23 Segher Boessenkool <segher@kernel.crashing.org>
>
> * dce.c (delete_unmarked_insns): Don't delete instructions with
> a REG_CFA_RESTORE note.
OK and can go in now IMHO.
jeff
next prev parent reply other threads:[~2016-09-26 16:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 8:22 [PATCH v3 0/5] Separate shrink-wrapping Segher Boessenkool
2016-09-23 8:22 ` [PATCH 2/5] dce: Don't dead-code delete separately wrapped restores Segher Boessenkool
2016-09-26 16:55 ` Jeff Law [this message]
2016-09-23 8:22 ` [PATCH 1/5] separate shrink-wrap: New command-line flag, status flag, hooks, and doc Segher Boessenkool
2016-09-26 17:02 ` Jeff Law
2016-09-23 8:23 ` [PATCH 3/5] regrename: Don't rename restores Segher Boessenkool
2016-09-26 16:44 ` Jeff Law
2016-09-23 8:33 ` [PATCH 4/5] shrink-wrap: Shrink-wrapping for separate components Segher Boessenkool
2016-09-27 21:25 ` Jeff Law
2016-09-28 9:26 ` Segher Boessenkool
2016-09-28 16:36 ` Jeff Law
2016-09-30 10:14 ` Segher Boessenkool
[not found] ` <20160930102908.GB14933@gate.crashing.org>
2016-09-30 10:52 ` Segher Boessenkool
2016-10-10 21:21 ` Jeff Law
2016-10-10 22:23 ` Segher Boessenkool
2016-09-23 8:44 ` [PATCH 5/5] rs6000: Separate shrink-wrapping Segher Boessenkool
2016-09-26 16:39 ` Jeff Law
2016-09-26 18:16 ` David Edelsohn
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=dd86bb38-bd12-ecc6-d3cc-baf0d0aa8856@redhat.com \
--to=law@redhat.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.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).