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/107505] [13 Regression] ICE: verify_flow_info failed (error: returns_twice call is not first in basic block 2)
Date: Mon, 07 Nov 2022 13:01:41 +0000	[thread overview]
Message-ID: <bug-107505-4-OGpwuPYSeM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107505-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107505

--- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Alexander Monakov <amonakov@gcc.gnu.org>:

https://gcc.gnu.org/g:5d060d8b0477ff4911f41c816281daaa24b41a13

commit r13-3753-g5d060d8b0477ff4911f41c816281daaa24b41a13
Author: Alexander Monakov <amonakov@ispras.ru>
Date:   Mon Nov 7 15:33:01 2022 +0300

    tree-ssa-sink: do not touch calls that return twice

    Avoid moving pure/const calls that may return twice in tree-ssa-sink:
    properly redirecting the associated abnormal edge is non-trivial.

    gcc/ChangeLog:

            PR tree-optimization/107505
            * tree-ssa-sink.cc (statement_sink_location): Additionally
            reject ECF_RETURNS_TWICE calls.

    gcc/testsuite/ChangeLog:

            PR tree-optimization/107505
            * gcc.dg/pr107505.c: New test.

  parent reply	other threads:[~2022-11-07 13:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02  7:41 [Bug tree-optimization/107505] New: " asolokha at gmx dot com
2022-11-02 16:27 ` [Bug tree-optimization/107505] " pinskia at gcc dot gnu.org
2022-11-02 18:49 ` amonakov at gcc dot gnu.org
2022-11-05 10:49 ` rguenth at gcc dot gnu.org
2022-11-07 13:01 ` cvs-commit at gcc dot gnu.org [this message]
2022-11-07 13:03 ` amonakov 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-107505-4-OGpwuPYSeM@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: 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).