From: Jakub Jelinek <jakub@redhat.com>
To: Richard Biener <rguenther@suse.de>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] tree-optimization/108691 - remove trigger-happy assert
Date: Tue, 21 Feb 2023 13:53:15 +0100 [thread overview]
Message-ID: <Y/S+u4hVd6NMu1o9@tucnak> (raw)
In-Reply-To: <20230221124800.25BFD13223@imap2.suse-dmz.suse.de>
On Tue, Feb 21, 2023 at 01:47:59PM +0100, Richard Biener wrote:
> The following gets rid of the idea that we should prevent setjmp
> like calls from popping up in uncontrolled way in the IL for now.
> The solution is probably to handle it similar as noreturn has
> the ctrl-altering flag on stmts, but use another flag, for example
> ctrl-receiving which would also make sure the stmt is first.
Yes, I'm all for it.
>
> Bootstrapped on x86_64-unknown-linux-gnu, testing in progress.
>
> OK?
>
> PR tree-optimization/108691
> * tree-ssa-dce.cc (eliminate_unnecessary_stmts): Remove
> assert about calls_setjmp not becoming true when it was false.
>
> * gcc.dg/pr108691.c: New testcase.
Ok.
Jakub
prev parent reply other threads:[~2023-02-21 12:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 12:47 Richard Biener
2023-02-21 12:53 ` Jakub Jelinek [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=Y/S+u4hVd6NMu1o9@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=rguenther@suse.de \
/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).