public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/96722] [8/9/10/11 Regression] Clobbers on NULL since r8-1519
Date: Mon, 24 Aug 2020 13:07:26 +0000	[thread overview]
Message-ID: <bug-96722-4-OSB8VFsvlw@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96722-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
On the CDDCE side, I'm afraid I have no idea what can be done.
The pass works by not considering clobber stmts necessary, and when about to
remove (all) clobbers as unnecessary, it instead attempts to keep them unless
they refer to SSA_NAMEs that weren't processed.
At that point, it has no idea if some clobber got turned from conditional into
unconditional, or the more likely case that it is kept as is.
So we'd need to remove (or somehow mark for guaranteed removal) the clobbers
earlier if they were turned from conditional into unconditional.

  parent reply	other threads:[~2020-08-24 13:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-20  9:30 [Bug tree-optimization/96722] New: " jakub at gcc dot gnu.org
2020-08-20  9:30 ` [Bug tree-optimization/96722] " jakub at gcc dot gnu.org
2020-08-20  9:39 ` marxin at gcc dot gnu.org
2020-08-20 13:59 ` marxin at gcc dot gnu.org
2020-08-24 11:30 ` jakub at gcc dot gnu.org
2020-08-24 12:08 ` rguenther at suse dot de
2020-08-24 13:07 ` jakub at gcc dot gnu.org [this message]
2020-08-24 13:49 ` rguenth at gcc dot gnu.org
2020-08-25 11:50 ` cvs-commit at gcc dot gnu.org
2020-08-25 17:45 ` cvs-commit at gcc dot gnu.org
2020-08-25 18:26 ` jakub at gcc dot gnu.org
2020-09-01  8:33 ` rguenth at gcc dot gnu.org
2020-09-01 10:56 ` [Bug tree-optimization/96722] [8/9 " jakub at gcc dot gnu.org
2020-09-16 19:23 ` cvs-commit at gcc dot gnu.org
2020-09-17 17:58 ` 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-96722-4-OSB8VFsvlw@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).