public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/63185] New: Improve DSE with branches
Date: Fri, 05 Sep 2014 10:51:00 -0000	[thread overview]
Message-ID: <bug-63185-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 63185
           Summary: Improve DSE with branches
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Keywords: missed-optimization
          Severity: enhancement
          Priority: P3
         Component: tree-optimization
          Assignee: unassigned at gcc dot gnu.org
          Reporter: glisse at gcc dot gnu.org

#include <stdlib.h>
#include <string.h>
void g();
void f(int n){
  char*p=malloc(1024);
  memset(p,8,1024);
  if(n)g();
}

We do not manage to remove the dead store (memset) because there is a PHI that
doesn't post-dominate the statement.


             reply	other threads:[~2014-09-05 10:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-05 10:51 glisse at gcc dot gnu.org [this message]
2014-09-05 13:03 ` [Bug tree-optimization/63185] " rguenth at gcc dot gnu.org
2014-09-05 13:27 ` glisse at gcc dot gnu.org
2014-10-16 12:16 ` rguenth at gcc dot gnu.org
2014-10-16 13:03 ` glisse at gcc dot gnu.org
2014-10-24 16:50 ` glisse at gcc dot gnu.org
2024-05-15 16:30 ` 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-63185-4@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).