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 tree-optimization/19703] [4.0 Regression] Poor optimisation of loop test, DOM causing unsigned to int and missing combine compares Date: Thu, 10 Feb 2005 23:46:00 -0000 [thread overview] Message-ID: <20050210210446.16929.qmail@sourceware.org> (raw) In-Reply-To: <20050130025905.19703.andrewhutchinson@cox.net> ------- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-10 21:04 ------- Lowering the priority as IV-OPTs has worked around DOM's problems. -- What |Removed |Added ---------------------------------------------------------------------------- Priority|P2 |P3 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19703
next prev parent reply other threads:[~2005-02-10 21:04 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-01-30 2:59 [Bug c/19703] New: Poor optimisation of loop test andrewhutchinson at cox dot net 2005-01-30 3:17 ` [Bug tree-optimization/19703] " pinskia at gcc dot gnu dot org 2005-01-30 3:17 ` pinskia at gcc dot gnu dot org 2005-01-30 4:58 ` andrewhutchinson at cox dot net 2005-01-30 5:25 ` [Bug tree-optimization/19703] [4.0 Regression] Poor optimisation of loop test, DOM causing unsigned to int and missing combine compares pinskia at gcc dot gnu dot org 2005-01-30 19:20 ` pinskia at gcc dot gnu dot org 2005-02-10 23:46 ` pinskia at gcc dot gnu dot org [this message] 2005-04-21 5:05 ` [Bug tree-optimization/19703] [4.0/4.1 " mmitchel at gcc dot gnu dot org 2005-06-26 18:03 ` pinskia at gcc dot gnu dot org 2005-07-08 1:43 ` mmitchel at gcc dot gnu dot org 2005-08-17 12:43 ` [Bug tree-optimization/19703] [4.0 " pinskia at gcc dot gnu dot org 2005-09-27 16:12 ` mmitchel at gcc dot gnu dot org [not found] <bug-19703-7648@http.gcc.gnu.org/bugzilla/> 2005-11-04 15:36 ` 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=20050210210446.16929.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).