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/110038] [14 Regression] ICE: in rewrite_expr_tree_parallel, at tree-ssa-reassoc.cc:5522 with --param=tree-reassoc-width=2147483647
Date: Wed, 31 May 2023 07:51:51 +0000	[thread overview]
Message-ID: <bug-110038-4-T46AXuD3c7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110038-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:80ee7d02e8db4893e104de02659fb71cc1dc81e9

commit r14-1425-g80ee7d02e8db4893e104de02659fb71cc1dc81e9
Author: Cui, Lili <lili.cui@intel.com>
Date:   Wed May 31 07:39:13 2023 +0000

    Fix ICE in rewrite_expr_tree_parallel

    1. Limit the value of tree-reassoc-width to IntegerRange(0, 256).
    2. Add width limit in rewrite_expr_tree_parallel.

    gcc/ChangeLog:

            PR tree-optimization/110038
            * params.opt: Add a limit on tree-reassoc-width.
            * tree-ssa-reassoc.cc
            (rewrite_expr_tree_parallel): Add width limit.

    gcc/testsuite/ChangeLog:

            PR tree-optimization/110038
            * gcc.dg/pr110038.c: New test.

  parent reply	other threads:[~2023-05-31  7:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30 10:49 [Bug tree-optimization/110038] New: " zsojka at seznam dot cz
2023-05-30 11:43 ` [Bug tree-optimization/110038] " rguenth at gcc dot gnu.org
2023-05-31  2:32 ` lili.cui at intel dot com
2023-05-31  7:51 ` cvs-commit at gcc dot gnu.org [this message]
2023-06-06 14:46 ` jamborm at gcc dot gnu.org
2023-06-07  1:57 ` lili.cui at intel dot com
2023-06-07  8: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-110038-4-T46AXuD3c7@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).