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/115646] [11/12/13/14 Regression] ICE in gen_conditions_for_pow_int_base, at tree-call-cdce.cc:587
Date: Mon, 08 Jul 2024 11:57:35 +0000	[thread overview]
Message-ID: <bug-115646-4-OwZFuTytT5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115646-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:078cdccc849831b8f1ff74b9ad16ce3f5aa172be

commit r14-10391-g078cdccc849831b8f1ff74b9ad16ce3f5aa172be
Author: Richard Biener <rguenther@suse.de>
Date:   Tue Jun 25 16:13:02 2024 +0200

    tree-optimization/115646 - ICE with pow shrink-wrapping from bitfield

    The following makes analysis and transform agree on constraints.

            PR tree-optimization/115646
            * tree-call-cdce.cc (check_pow): Check for bit_sz values
            as allowed by transform.

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

    (cherry picked from commit 453b1d291d1a0f89087ad91cf6b1bed1ec68eff3)

  parent reply	other threads:[~2024-07-08 11:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-25 13:02 [Bug c/115646] New: [gcc][trunk] " 141242068 at smail dot nju.edu.cn
2024-06-25 14:11 ` [Bug c/115646] " rguenth at gcc dot gnu.org
2024-06-26  6:55 ` cvs-commit at gcc dot gnu.org
2024-06-26  6:57 ` [Bug tree-optimization/115646] [11/12/13/14 Regression] " rguenth at gcc dot gnu.org
2024-07-08 11:57 ` cvs-commit at gcc dot gnu.org [this message]
2024-07-19 13:25 ` [Bug tree-optimization/115646] [12/13 " rguenth at gcc dot gnu.org
2024-09-18 10:32 ` cvs-commit 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-115646-4-OwZFuTytT5@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).