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/109417] [13 Regression] ICE on valid code at -O3 on x86_64-linux-gnu: Segmentation fault since r13-6945
Date: Wed, 26 Apr 2023 19:25:53 +0000	[thread overview]
Message-ID: <bug-109417-4-ojnFpJGp0m@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109417-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andrew Macleod <amacleod@gcc.gnu.org>:

https://gcc.gnu.org/g:40c7f943e882e8c5eccf45fc28146559f446764d

commit r14-271-g40c7f943e882e8c5eccf45fc28146559f446764d
Author: Andrew MacLeod <amacleod@redhat.com>
Date:   Tue Apr 25 15:33:52 2023 -0400

    Don't save ssa-name pointer in dependency cache.

    If the direct dependence fields point directly to an ssa-name,
    its possible that an optimization frees an ssa-name, and the value
    pointed to may now be in the free list.   Simply maintain the ssa
    version number instead.

            PR tree-optimization/109417
            * gimple-range-gori.cc (range_def_chain::register_dependency):
            Save the ssa version number, not the pointer.
            (gori_compute::may_recompute_p): No need to check if a dependency
            is in the free list.
            * gimple-range-gori.h (class range_def_chain): Change ssa1 and ssa2
            fields to be unsigned int instead of trees.
            (ange_def_chain::depend1): Adjust.
            (ange_def_chain::depend2): Adjust.
            * gimple-range.h: Include "ssa.h" to inline ssa_name().

      parent reply	other threads:[~2023-04-26 19:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-05  7:54 [Bug tree-optimization/109417] New: ICE on valid code at -O3 on x86_64-linux-gnu: Segmentation fault zhendong.su at inf dot ethz.ch
2023-04-05  9:26 ` [Bug tree-optimization/109417] [13 Regression] " xry111 at gcc dot gnu.org
2023-04-05 18:24 ` [Bug tree-optimization/109417] [13 Regression] ICE on valid code at -O3 on x86_64-linux-gnu: Segmentation fault since r13-6945 jakub at gcc dot gnu.org
2023-04-05 19:55 ` amacleod at redhat dot com
2023-04-06 12:32 ` cvs-commit at gcc dot gnu.org
2023-04-06 12:32 ` amacleod at redhat dot com
2023-04-26 19:25 ` 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-109417-4-ojnFpJGp0m@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).