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/113673] [12/13/14/15 Regression] ICE: verify_flow_info failed: BB 5 cannot throw but has an EH edge with -Os -finstrument-functions -fnon-call-exceptions -ftrapv
Date: Mon, 24 Jun 2024 14:36:01 +0000	[thread overview]
Message-ID: <bug-113673-4-B3h6BR6gWB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113673-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Roger Sayle <sayle@gcc.gnu.org>:

https://gcc.gnu.org/g:d8b05aef77443e1d3d8f3f5d2c56ac49a503fee3

commit r15-1584-gd8b05aef77443e1d3d8f3f5d2c56ac49a503fee3
Author: Roger Sayle <roger@nextmovesoftware.com>
Date:   Mon Jun 24 15:34:03 2024 +0100

    PR tree-optimization/113673: Avoid load merging when potentially trapping.

    This patch fixes PR tree-optimization/113673, a P2 ice-on-valid regression
    caused by load merging of (ptr[0]<<8)+ptr[1] when -ftrapv has been
    specified.  When the operator is | or ^ this is safe, but for addition
    of signed integer types, a trap may be generated/required, so merging this
    idiom into a single non-trapping instruction is inappropriate, confusing
    the compiler by transforming a basic block with an exception edge into one
    without.

    This revision implements Richard Biener's feedback to add an early check
    for stmt_can_throw_internal (cfun, stmt) to prevent transforming in the
    presence of any statement that could trap, not just overflow on addition.
    The one other tweak included in this patch is to mark the local function
    find_bswap_or_nop_load as static ensuring that it isn't called from outside
    this file, and guaranteeing that it is dominated by stmt_can_throw_internal
    checking.

    2024-06-24  Roger Sayle  <roger@nextmovesoftware.com>
                Richard Biener  <rguenther@suse.de>

    gcc/ChangeLog
            PR tree-optimization/113673
            * gimple-ssa-store-merging.cc (find_bswap_or_nop_load): Make
static.
            (find_bswap_or_nop_1): Avoid transformations (load merging) when
            stmt_can_throw_internal indicates that a statement can trap.

    gcc/testsuite/ChangeLog
            PR tree-optimization/113673
            * g++.dg/pr113673.C: New test case.

  parent reply	other threads:[~2024-06-24 14:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30 19:00 [Bug tree-optimization/113673] New: [12/13/14 " zsojka at seznam dot cz
2024-01-30 19:03 ` [Bug tree-optimization/113673] " pinskia at gcc dot gnu.org
2024-01-30 19:09 ` pinskia at gcc dot gnu.org
2024-01-31  8:20 ` rguenth at gcc dot gnu.org
2024-02-08 16:52 ` mjires at gcc dot gnu.org
2024-02-08 21:36 ` roger at nextmovesoftware dot com
2024-02-08 22:01 ` pinskia at gcc dot gnu.org
2024-04-26 21:36 ` [Bug tree-optimization/113673] [12/13/14/15 " roger at nextmovesoftware dot com
2024-06-20  9:14 ` rguenth at gcc dot gnu.org
2024-06-24 14:36 ` cvs-commit at gcc dot gnu.org [this message]
2024-06-26 14:41 ` [Bug tree-optimization/113673] [12/13/14 " roger at nextmovesoftware dot com

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-113673-4-B3h6BR6gWB@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).