public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/110390] ICE on valid code on x86_64-linux-gnu with sel-scheduling: in av_set_could_be_blocked_by_bookkeeping_p, at sel-sched.cc:3609
Date: Sun, 12 Nov 2023 18:43:04 +0000	[thread overview]
Message-ID: <bug-110390-4-OPJixKgfz1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110390-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Fixed by r14-3414-g0cfc9c953d0221:

0cfc9c953d0221ec3971a25e6509ebe1041f142e is the first new commit
commit 0cfc9c953d0221ec3971a25e6509ebe1041f142e
Author: Andrew MacLeod <amacleod@redhat.com>
Date:   Thu Aug 17 12:34:59 2023 -0400

    Phi analyzer - Initialize with range instead of a tree.

    Rangers PHI analyzer currently only allows a single initializer to a group.
    This patch changes that to use an inialization range, which is
    cumulative of all integer constants, plus a single symbolic value.
    There is no other change to group functionality.

    This patch also changes the way PHI groups are printed so they show up in
the
    listing as they are encountered, rather than as a list at the end.  It
    was more difficult to see what was going on previously.

  parent reply	other threads:[~2023-11-12 18:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-24 12:52 [Bug rtl-optimization/110390] New: " zhendong.su at inf dot ethz.ch
2023-06-24 19:42 ` [Bug rtl-optimization/110390] " zhendong.su at inf dot ethz.ch
2023-11-12 12:04 ` tkoenig at gcc dot gnu.org
2023-11-12 18:43 ` tkoenig at gcc dot gnu.org [this message]
2023-11-12 19:11 ` pinskia at gcc dot gnu.org
2023-11-14  6:45 ` [Bug rtl-optimization/110390] ICE on valid code on x86_64-linux-gnu with sel-scheduling: in av_set_could_be_blocked_by_bookkeeping_p, at sel-sched.cc:3609 since r13-3596-ge7310e24b1c0ca tkoenig at gcc dot gnu.org
2023-11-14  6:52 ` pinskia at gcc dot gnu.org
2023-11-15  6:26 ` [Bug rtl-optimization/110390] [13/14 regression] " sjames at gcc dot gnu.org
2024-01-31 14:32 ` rguenth at gcc dot gnu.org
2024-03-04  4:56 ` law at gcc dot gnu.org
2024-05-21  9:16 ` [Bug rtl-optimization/110390] [13/14/15 " jakub 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-110390-4-OPJixKgfz1@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).