public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/106923] [13 Regression] ICE in eliminate_unnecessary_stmts, at tree-ssa-dce.cc:1512 since r13-2518-ga262f969d6fd936f Date: Tue, 07 Feb 2023 09:35:19 +0000 [thread overview] Message-ID: <bug-106923-4-fWdZiASo9I@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106923-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106923 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:5321d53279a60ee589a3c9779beb46503f9fc49f commit r13-5728-g5321d53279a60ee589a3c9779beb46503f9fc49f Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Feb 7 10:34:45 2023 +0100 ipa-split: Don't split returns_twice functions [PR106923] As discussed in the PR, returns_twice functions are rare/special beasts that need special treatment in the cfg, and inside of their bodies we don't know which part actually works the weird returns twice way (either in the fork/vfork sense, or in the setjmp) and aren't updating ab edges to reflect that. I think easiest is just to never split these, like we already never split noreturn or malloc functions. 2023-02-07 Jakub Jelinek <jakub@redhat.com> PR tree-optimization/106923 * ipa-split.cc (execute_split_functions): Don't split returns_twice functions. * gcc.dg/pr106923.c: New test.
next prev parent reply other threads:[~2023-02-07 9:35 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-13 9:40 [Bug tree-optimization/106923] New: [13 Regression] ICE in eliminate_unnecessary_stmts, at tree-ssa-dce.cc:1512 asolokha at gmx dot com 2022-09-13 11:33 ` [Bug tree-optimization/106923] [13 Regression] ICE in eliminate_unnecessary_stmts, at tree-ssa-dce.cc:1512 since r13-2518-ga262f969d6fd936f marxin at gcc dot gnu.org 2022-09-13 12:34 ` rguenth at gcc dot gnu.org 2022-10-18 8:46 ` rguenth at gcc dot gnu.org 2022-11-25 7:43 ` rguenth at gcc dot gnu.org 2023-02-06 13:26 ` jakub at gcc dot gnu.org 2023-02-07 9:35 ` cvs-commit at gcc dot gnu.org [this message] 2023-02-07 9:41 ` jakub at gcc dot gnu.org 2023-07-28 7:51 ` cvs-commit at gcc dot gnu.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=bug-106923-4-fWdZiASo9I@http.gcc.gnu.org/bugzilla/ \ --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: linkBe 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).