public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/63841] Incorrect strlen optimization after complete unroll Date: Thu, 13 Nov 2014 09:20:00 -0000 [thread overview] Message-ID: <bug-63841-4-23U8r7Cfj8@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63841-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63841 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |wrong-code Status|UNCONFIRMED |NEW Last reconfirmed| |2014-11-13 CC| |jakub at gcc dot gnu.org Ever confirmed|0 |1 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed. Seems to be an opportunity to remove the clobber to be able to remove a dead store... ;)
next prev parent reply other threads:[~2014-11-13 9:20 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-11-12 22:00 [Bug tree-optimization/63841] New: " tejohnson at google dot com 2014-11-12 22:01 ` [Bug tree-optimization/63841] " tejohnson at google dot com 2014-11-13 9:20 ` rguenth at gcc dot gnu.org [this message] 2014-11-13 14:27 ` [Bug tree-optimization/63841] [4.8/4.9/5 Regression] " tejohnson at google dot com 2014-11-13 15:37 ` tejohnson at gcc dot gnu.org 2014-11-13 21:51 ` tejohnson at gcc dot gnu.org 2014-11-14 6:36 ` tejohnson at gcc dot gnu.org 2014-11-17 21:16 ` jakub at gcc dot gnu.org 2014-11-17 21:17 ` [Bug tree-optimization/63841] [4.8 " jakub at gcc dot gnu.org 2014-11-17 21:27 ` tejohnson at google dot com 2014-11-18 14:21 ` tejohnson at gcc dot gnu.org 2014-11-20 14:30 ` tejohnson at gcc dot gnu.org 2014-12-10 13:16 ` 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-63841-4-23U8r7Cfj8@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).