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/101088] [12 Regression] ICE in sm_seq_valid_bb, at tree-ssa-loop-im.c:2383
Date: Wed, 07 Jul 2021 14:06:47 +0000	[thread overview]
Message-ID: <bug-101088-4-Ya4Wx8xAgv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101088-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Richard Biener
<rguenth@gcc.gnu.org>:

https://gcc.gnu.org/g:91fc9610464281bb28e3c6529399fdcfb57fa812

commit r11-8696-g91fc9610464281bb28e3c6529399fdcfb57fa812
Author: Richard Biener <rguenther@suse.de>
Date:   Wed Jun 16 09:49:18 2021 +0200

    tree-optimization/101088 - fix SM invalidation issue

    When we face a sm_ord vs sm_unord for the same ref during
    store sequence merging we assert that the ref is already marked
    unsupported.  But it can be that it will only be marked so
    during the ongoing merging so instead of asserting mark it here.

    Also apply some optimization to not waste resources to search
    for already unsupported refs.

    2021-06-16  Richard Biener  <rguenther@suse.de>

            PR tree-optimization/101088
            * tree-ssa-loop-im.c (sm_seq_valid_bb): Only look for
            supported refs on edges.  Do not assert same ref but
            different kind stores are unsuported but mark them so.
            (hoist_memory_references): Only look for supported refs
            on exits.

            * gcc.dg/torture/pr101088.c: New testcase.

    (cherry picked from commit 43fc4234ad3d9302d3460385b6fdb5e3f59b6986)

      parent reply	other threads:[~2021-07-07 14:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-16  3:10 [Bug tree-optimization/101088] New: " asolokha at gmx dot com
2021-06-16  6:59 ` [Bug tree-optimization/101088] " rguenth at gcc dot gnu.org
2021-06-16  8:57 ` marxin at gcc dot gnu.org
2021-06-16 10:16 ` cvs-commit at gcc dot gnu.org
2021-06-16 10:16 ` rguenth at gcc dot gnu.org
2021-07-07 14:06 ` cvs-commit at gcc dot gnu.org [this message]

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-101088-4-Ya4Wx8xAgv@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).