public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "phython at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/21559] [4.1 Regression] missed jump threading Date: Sun, 31 Jul 2005 05:46:00 -0000 [thread overview] Message-ID: <20050731054540.15214.qmail@sourceware.org> (raw) In-Reply-To: <20050513224225.21559.pinskia@gcc.gnu.org> ------- Additional Comments From phython at gcc dot gnu dot org 2005-07-31 05:45 ------- I would really prefer option b, where we keep VRP information persistant. That way fold can use VRP information when available. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21559
next prev parent reply other threads:[~2005-07-31 5:46 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-05-13 22:42 [Bug tree-optimization/21559] New: " pinskia at gcc dot gnu dot org 2005-05-13 22:43 ` [Bug tree-optimization/21559] " pinskia at gcc dot gnu dot org 2005-05-16 0:07 ` steven at gcc dot gnu dot org 2005-07-27 17:18 ` law at redhat dot com 2005-07-28 22:03 ` law at redhat dot com 2005-07-29 12:30 ` pinskia at gcc dot gnu dot org 2005-07-31 5:46 ` phython at gcc dot gnu dot org [this message] [not found] <bug-21559-6528@http.gcc.gnu.org/bugzilla/> 2005-10-27 0:12 ` pinskia at gcc dot gnu dot org 2005-10-29 18:09 ` pinskia at gcc dot gnu dot org 2005-10-30 23:32 ` 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=20050731054540.15214.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).