From: Michael Matz <matz@suse.de>
To: Peter Bergner <bergner@vnet.ibm.com>
Cc: Jeff Law <law@redhat.com>,
Richard Biener <richard.guenther@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [RFA][PATCH][PR middle-end/61118] Improve tree CFG accuracy for setjmp/longjmp
Date: Thu, 08 Mar 2018 12:54:00 -0000 [thread overview]
Message-ID: <alpine.LSU.2.21.1803081251270.5310@wotan.suse.de> (raw)
In-Reply-To: <d3124b8f-99f7-f9ca-233e-595379fa7f4e@vnet.ibm.com>
Hi,
On Wed, 7 Mar 2018, Peter Bergner wrote:
> On 3/7/18 12:01 AM, Jeff Law wrote:
> > I believe so by nature that the setjmp dominates the longjmp sites and
> > thus also dominates the dispatcher. But it's something I want to
> > explicitly check before resubmitting.
>
> Are we sure a setjmp has to dominate its longjmp sites?
No, they don't have to dominate. For lack of better term I used something
like "ordered after" in my mails :)
> Couldn't you have something like:
Yeah, exactly.
Ciao,
Michael.
next prev parent reply other threads:[~2018-03-08 12:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-28 0:16 Jeff Law
2018-02-28 10:43 ` Richard Biener
2018-02-28 10:48 ` Richard Biener
2018-02-28 15:46 ` Jeff Law
2018-02-28 17:35 ` Jeff Law
2018-03-01 10:45 ` Richard Biener
2018-03-05 18:30 ` Michael Matz
2018-03-05 19:08 ` Jeff Law
2018-03-05 19:30 ` Michael Matz
2018-03-06 3:41 ` Jeff Law
2018-03-06 8:57 ` Richard Biener
2018-03-07 6:01 ` Jeff Law
2018-03-08 0:04 ` Peter Bergner
2018-03-08 12:54 ` Michael Matz [this message]
2018-03-08 13:22 ` Richard Biener
2018-03-08 13:26 ` Richard Biener
2018-03-08 13:28 ` Michael Matz
2018-03-09 19:42 ` Jeff Law
2018-03-09 20:20 ` Richard Biener
2018-03-09 19:45 ` Jeff Law
2018-03-06 14:17 ` Michael Matz
2018-03-06 14:43 ` Richard Biener
2018-03-06 16:31 ` Michael Matz
2018-03-02 22:18 ` Jeff Law
2018-03-02 23:07 ` Jakub Jelinek
2018-03-02 23:17 ` Jeff Law
2018-03-05 14:07 ` Richard Biener
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=alpine.LSU.2.21.1803081251270.5310@wotan.suse.de \
--to=matz@suse.de \
--cc=bergner@vnet.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=richard.guenther@gmail.com \
/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).