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] Improve DSE with branches Date: Thu, 16 Oct 2014 13:03:00 -0000 [thread overview] Message-ID: <bug-63185-4-yUPHKKvoJO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63185-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63185 --- Comment #4 from Marc Glisse <glisse at gcc dot gnu.org> --- (In reply to Richard Biener from comment #3) > Btw, what was the original testcase? Sorry, I don't remember. Probably something involving std::vector or std::string. Since llvm optimizes it just fine, I hadn't realized it would be so hard. > That is, without making the walk very much more expensive there isn't > anything we can do about this. Ok, thanks for looking at it. Down to P5?
next prev parent reply other threads:[~2014-10-16 13:03 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-09-05 10:51 [Bug tree-optimization/63185] New: " glisse at gcc dot gnu.org 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 [this message] 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-yUPHKKvoJO@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: linkBe 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).