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/105173] [10/11 Regression] ICE: during GIMPLE pass: reassoc: verify_ssa failed (definition in block 2 follows the use) at -Ofast with decimals since r7-950-g8a85cee26eabf5cf
Date: Thu, 19 May 2022 14:03:15 +0000	[thread overview]
Message-ID: <bug-105173-4-HU1ldMeQCR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105173-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 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:f4f2bd4edea8beabcf9caea98f951dcac612b126

commit r11-10016-gf4f2bd4edea8beabcf9caea98f951dcac612b126
Author: Richard Biener <rguenther@suse.de>
Date:   Wed Apr 6 11:43:01 2022 +0200

    tree-optimization/105173 - fix insertion logic in reassoc

    The find_insert_point logic around deciding whether to insert
    before or after the found insertion point does not handle
    the case of _12 = ..;, _12, 1.0 well.  The following puts the
    logic into find_insert_point itself instead.

    2022-04-06  Richard Biener  <rguenther@suse.de>

            PR tree-optimization/105173
            * tree-ssa-reassoc.c (find_insert_point): Get extra
            insert_before output argument and compute it.
            (insert_stmt_before_use): Adjust.
            (rewrite_expr_tree): Likewise.

            * gcc.dg/pr105173.c: New testcase.

    (cherry picked from commit e1a5e7562d53a8d2256f754714b06595bea72196)

  parent reply	other threads:[~2022-05-19 14:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-06  4:21 [Bug tree-optimization/105173] New: [10/11/12 Regression] ICE: during GIMPLE pass: reassoc: verify_ssa failed (definition in block 2 follows the use) at -Ofast with decimals zsojka at seznam dot cz
2022-04-06  8:10 ` [Bug tree-optimization/105173] " rguenth at gcc dot gnu.org
2022-04-06  9:20 ` [Bug tree-optimization/105173] [10/11/12 Regression] ICE: during GIMPLE pass: reassoc: verify_ssa failed (definition in block 2 follows the use) at -Ofast with decimals since r7-950-g8a85cee26eabf5cf marxin at gcc dot gnu.org
2022-04-06  9:40 ` rguenth at gcc dot gnu.org
2022-04-06 11:15 ` cvs-commit at gcc dot gnu.org
2022-04-06 11:16 ` [Bug tree-optimization/105173] [10/11 " rguenth at gcc dot gnu.org
2022-05-19 14:03 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-27 13:15 ` [Bug tree-optimization/105173] [10 " cvs-commit at gcc dot gnu.org
2022-05-27 13:17 ` rguenth 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-105173-4-HU1ldMeQCR@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).