public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dberlin at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/19624] PRE pessimizes ivopts Date: Tue, 25 Jan 2005 15:23:00 -0000 [thread overview] Message-ID: <20050125152302.9146.qmail@sourceware.org> (raw) In-Reply-To: <20050125144432.19624.rguenth@tat.physik.uni-tuebingen.de> ------- Additional Comments From dberlin at gcc dot gnu dot org 2005-01-25 15:23 ------- Just as an FYI, i have absoutely no plans to make it so ivopts and PRE interact perfectly. I only plan to disable transforms in PRE that are always unprofitable. -- What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |dberlin at gcc dot gnu dot |dot org |org Status|UNCONFIRMED |ASSIGNED Ever Confirmed| |1 Last reconfirmed|0000-00-00 00:00:00 |2005-01-25 15:23:01 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19624
next prev parent reply other threads:[~2005-01-25 15:23 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-01-25 14:45 [Bug tree-optimization/19624] New: " rguenth at tat dot physik dot uni-tuebingen dot de 2005-01-25 14:45 ` [Bug tree-optimization/19624] " rguenth at tat dot physik dot uni-tuebingen dot de 2005-01-25 14:52 ` rguenth at tat dot physik dot uni-tuebingen dot de 2005-01-25 15:23 ` dberlin at gcc dot gnu dot org [this message] 2005-01-25 15:27 ` rguenth at tat dot physik dot uni-tuebingen dot de 2005-01-25 15:35 ` dberlin at dberlin dot org 2005-01-30 19:09 ` dberlin at gcc dot gnu dot org 2005-01-30 19:09 ` cvs-commit at gcc dot gnu dot org 2005-01-30 19:10 ` pinskia at gcc dot gnu dot org 2005-01-30 20:56 ` steven 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=20050125152302.9146.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).