public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/102844] [9/10/11/12/13 Regression] DOM jump threading not copying block that became non-empty
Date: Fri, 20 May 2022 15:11:33 +0000	[thread overview]
Message-ID: <bug-102844-4-PVOp4jiAsG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102844-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #27 from Jeffrey A. Law <law at gcc dot gnu.org> ---
We're not using the backward threader to replace DOM's threader yet.  I've got
a TODO to push on Aldy's patch, but haven't been able to get to it over the
last couple weeks.  It's an, umm, busy time for us right now.

There's really only one issue we need to hash out in Aldy's work and there's a
couple proposed workarounds/interm solutions on our way to removing both the
forward threader and DOM itself.

  parent reply	other threads:[~2022-05-20 15:11 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-19 17:45 [Bug c/102844] New: gcc-9.x miscompiles unsigned char expression in switch breiten at lexmark dot com
2021-10-19 17:58 ` [Bug tree-optimization/102844] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org
2021-10-19 18:11 ` pinskia at gcc dot gnu.org
2021-10-19 18:13 ` pinskia at gcc dot gnu.org
2021-10-19 18:23 ` [Bug tree-optimization/102844] [9/10/11/12 Regression] vrp inserting assert causes miscompiling when doing update_ssa pinskia at gcc dot gnu.org
2021-10-20  7:10 ` rguenth at gcc dot gnu.org
2021-10-20  7:44 ` rguenth at gcc dot gnu.org
2021-10-20  7:49 ` rguenth at gcc dot gnu.org
2021-10-20  8:08 ` marxin at gcc dot gnu.org
2021-10-20  8:28 ` rguenth at gcc dot gnu.org
2021-10-20  8:33 ` marxin at gcc dot gnu.org
2021-10-20  8:59 ` rguenth at gcc dot gnu.org
2021-10-20  9:00 ` rguenth at gcc dot gnu.org
2021-10-20  9:03 ` rguenth at gcc dot gnu.org
2021-10-20  9:08 ` rguenth at gcc dot gnu.org
2021-10-20  9:19 ` rguenth at gcc dot gnu.org
2021-10-20  9:21 ` aldyh at gcc dot gnu.org
2021-10-20  9:30 ` rguenther at suse dot de
2021-10-20  9:47 ` aldyh at gcc dot gnu.org
2021-10-20  9:50 ` rguenth at gcc dot gnu.org
2021-10-20  9:50 ` rguenth at gcc dot gnu.org
2021-10-20 10:56 ` marxin at gcc dot gnu.org
2021-10-20 12:49 ` [Bug tree-optimization/102844] [9/10/11/12 Regression] DOM jump threading not copying block that became non-empty amacleod at redhat dot com
2021-10-20 16:13 ` law at gcc dot gnu.org
2021-10-21  6:02 ` rguenth at gcc dot gnu.org
2022-05-20  8:24 ` [Bug tree-optimization/102844] [9/10/11/12/13 " rguenth at gcc dot gnu.org
2022-05-20 12:01 ` aldyh at gcc dot gnu.org
2022-05-20 15:11 ` law at gcc dot gnu.org [this message]
2022-05-20 15:33 ` aldyh at gcc dot gnu.org
2022-05-27  9:46 ` [Bug tree-optimization/102844] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:46 ` jakub at gcc dot gnu.org
2023-01-19 13:26 ` rguenth at gcc dot gnu.org
2023-07-07 10:41 ` [Bug tree-optimization/102844] [11/12/13/14 " rguenth at gcc dot gnu.org
2023-09-19 11:24 ` rguenth at gcc dot gnu.org
2023-09-19 11:25 ` [Bug tree-optimization/102844] [11/12/13 " 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-102844-4-PVOp4jiAsG@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).