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/19832] don't remove an if when we know the value is the same as with the if (subtraction)
Date: Wed, 09 Feb 2005 07:46:00 -0000 [thread overview]
Message-ID: <20050208233409.21431.qmail@sourceware.org> (raw)
In-Reply-To: <20050208231758.19832.christophe.jaillet@wanadoo.fr>
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-08 23:34 -------
Confirmed, here is the full testcase by the way:
int f(int i, int j)
{
if (i!=j)
return i - j;
return 0;
}
Note I did not say the patch is useless but I just wantted to say that it would be useful if gcc did this for
us instead of changing the code. Anyways this can be done with PHI-OPT, I will try to look into this
doing this for 4.1. Your patch should be still considered.
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |pinskia at gcc dot gnu dot
| |org
Severity|normal |enhancement
Status|UNCONFIRMED |NEW
Component|c |tree-optimization
Ever Confirmed| |1
Keywords| |missed-optimization
Last reconfirmed|0000-00-00 00:00:00 |2005-02-08 23:34:07
date| |
Summary|Missed optimisation |don't remove an if when we
| |know the value is the same
| |as with the if (subtraction)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19832
next prev parent reply other threads:[~2005-02-08 23:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-09 7:41 [Bug c/19832] New: Missed optimisation christophe dot jaillet at wanadoo dot fr
2005-02-09 7:46 ` pinskia at gcc dot gnu dot org [this message]
[not found] <bug-19832-4@http.gcc.gnu.org/bugzilla/>
2011-08-13 1:39 ` [Bug tree-optimization/19832] don't remove an if when we know the value is the same as with the if (subtraction) jimis at gmx dot net
2011-08-13 2:21 ` jimis at gmx dot net
2012-08-06 11:41 ` rguenth at gcc dot gnu.org
2023-05-06 21:15 ` pinskia at gcc dot gnu.org
2023-05-06 23:12 ` pinskia at gcc dot gnu.org
2023-05-06 23:13 ` pinskia at gcc dot gnu.org
2023-08-31 1:03 ` pinskia at gcc dot gnu.org
2023-08-31 4:48 ` pinskia at gcc dot gnu.org
2023-08-31 18:03 ` pinskia at gcc dot gnu.org
2023-09-01 6:58 ` cvs-commit at gcc dot gnu.org
2023-09-01 6:58 ` pinskia at gcc dot gnu.org
2023-09-01 12:23 ` cvs-commit at gcc dot gnu.org
2023-12-25 4:02 ` cvs-commit 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=20050208233409.21431.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: link
Be 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).