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/95113] [10/11 Regression] Wrong code w/ -O2 -fexceptions -fnon-call-exceptions
Date: Thu, 04 Jun 2020 15:04:19 +0000	[thread overview]
Message-ID: <bug-95113-4-IkJR9HLtiD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95113-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Martin Jambor <jamborm@gcc.gnu.org>:

https://gcc.gnu.org/g:1980ffec48c6fa41396bea66366f2e591798e1e1

commit r11-935-g1980ffec48c6fa41396bea66366f2e591798e1e1
Author: Martin Jambor <mjambor@suse.cz>
Date:   Thu Jun 4 17:03:27 2020 +0200

    ipa-sra: Do not remove statements necessary because of non-call EH (PR
95113)

    PR 95113 revealed that when reasoning about which parameters are dead,
    IPA-SRA does not perform the same check related to non-call exceptions
    as tree DCE.  It most certainly should and so this patch moves the
    condition used in tree-ssa-dce.c into a separate predicate (in
    tree-eh.c) and uses it from both places.

    gcc/ChangeLog:

    2020-05-27  Martin Jambor  <mjambor@suse.cz>

            PR ipa/95113
            * tree-ssa-dce.c (mark_stmt_if_obviously_necessary): Move non-call
            exceptions check to...
            * tree-eh.c (stmt_unremovable_because_of_non_call_eh_p): ...this
            new function.
            * tree-eh.h (stmt_unremovable_because_of_non_call_eh_p): Declare
it.
            * ipa-sra.c (isra_track_scalar_value_uses): Use it.  New parameter
            fun.

    gcc/testsuite/ChangeLog:

    2020-05-27  Martin Jambor  <mjambor@suse.cz>

            PR ipa/95113
            * gcc.dg/ipa/pr95113.c: New test.

  parent reply	other threads:[~2020-06-04 15:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13 17:55 [Bug tree-optimization/95113] New: " asolokha at gmx dot com
2020-05-13 18:06 ` [Bug tree-optimization/95113] " jakub at gcc dot gnu.org
2020-05-13 18:15 ` jakub at gcc dot gnu.org
2020-05-13 18:29 ` asolokha at gmx dot com
2020-05-14  6:20 ` rguenth at gcc dot gnu.org
2020-05-28 12:35 ` jamborm at gcc dot gnu.org
2020-06-04 15:04 ` cvs-commit at gcc dot gnu.org [this message]
2020-06-08 18:16 ` cvs-commit at gcc dot gnu.org
2020-06-08 18:18 ` jamborm at gcc dot gnu.org
2020-06-08 18:18 ` jamborm 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-95113-4-IkJR9HLtiD@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).