public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/38856] loop iv detection failure, SSA autoincrement Date: Thu, 15 Jan 2009 18:42:00 -0000 [thread overview] Message-ID: <20090115184152.16944.qmail@sourceware.org> (raw) In-Reply-To: <bug-38856-17190@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from pinskia at gcc dot gnu dot org 2009-01-15 18:41 ------- Well first off, iv-opts on the tree level should be the place where autoincrement is helped out. See PR 31849 which I think this is a duplicate of. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38856
next prev parent reply other threads:[~2009-01-15 18:42 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-01-15 18:24 [Bug c/38856] New: " sergei_lus at yahoo dot com 2009-01-15 18:42 ` pinskia at gcc dot gnu dot org [this message] 2009-01-15 21:03 ` [Bug c/38856] " sergei_lus at yahoo dot com 2009-01-15 21:13 ` [Bug middle-end/38856] loop iv detection failure pinskia at gcc dot gnu dot org 2009-01-15 21:17 ` pinskia at gcc dot gnu dot org 2009-01-16 9:57 ` rguenth at gcc dot gnu dot org 2009-01-16 11:46 ` Andrew Thomas Pinski 2009-01-16 11:46 ` pinskia at gmail dot com 2009-01-16 18:53 ` pinskia at gcc dot gnu dot 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=20090115184152.16944.qmail@sourceware.org \ --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).