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 c++/106057] Missed stmt_can_throw_external check in stmt_kills_ref_p
Date: Fri, 24 Jun 2022 11:54:05 +0000	[thread overview]
Message-ID: <bug-106057-4-vYf8Eemmxz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106057-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:7fd34782b95bbe1b4dc9936b8923f86d4aaee379

commit r13-1241-g7fd34782b95bbe1b4dc9936b8923f86d4aaee379
Author: Jan Hubicka <jh@suse.cz>
Date:   Fri Jun 24 13:52:44 2022 +0200

    Fix stmt_kills_ref_p WRT external throws

    Add missing check to stmt_kills_ref_p for case that function
    is terminated by EH before call return value kills the ref. In the PR
    I tried to construct testcase but I don't know how to do that until I
    annotate EH code with fnspec attributes which I will do in separate patch
    and add a testcase.

            PR ipa/106057
            * tree-ssa-alias.cc (stmt_kills_ref_p): Check for external throw.

  parent reply	other threads:[~2022-06-24 11:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22 16:26 [Bug c++/106057] New: " hubicka at gcc dot gnu.org
2022-06-22 16:51 ` [Bug c++/106057] " hubicka at gcc dot gnu.org
2022-06-23  9:34 ` hubicka at gcc dot gnu.org
2022-06-24 11:54 ` cvs-commit at gcc dot gnu.org [this message]
2022-08-12 14:26 ` cvs-commit at gcc dot gnu.org
2023-04-27 13:18 ` 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-106057-4-vYf8Eemmxz@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).