public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/18832] missed jump threading with ||
Date: Sat, 23 Apr 2005 01:08:00 -0000 [thread overview]
Message-ID: <20050423010819.19927.qmail@sourceware.org> (raw)
In-Reply-To: <20041204193149.18832.pinskia@gcc.gnu.org>
------- Additional Comments From law at redhat dot com 2005-04-23 01:08 -------
The threading issues in f0 have been addressed. Some simple code hoisting would
make f0 slightly better from a code size standpoint, but probably wouldn't
help runtime.
The lameness in f1 isn't really a jump threading problem. We have a merge
point before the second pair of tests which is going to make it damn near
impossible to track the values well enough to optimize this code. This
isn't a jump threading problem.
f2 and f3 look good.
Basically there's no jump threading issues left here.
(In reply to comment #1)
> Oh and this one too:
> int f3(int c,int a, int b)
> {
> if (a== 0||b==0) c+=2;
> return c;
> }
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18832
next prev parent reply other threads:[~2005-04-23 1:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-04 19:31 [Bug tree-optimization/18832] New: " pinskia at gcc dot gnu dot org
2004-12-04 19:43 ` [Bug tree-optimization/18832] " pinskia at gcc dot gnu dot org
2004-12-05 16:16 ` pinskia at gcc dot gnu dot org
2005-02-15 1:26 ` law at redhat dot com
2005-04-23 1:08 ` law at redhat dot com [this message]
2005-04-25 18:20 ` pinskia at gcc dot gnu dot org
[not found] <bug-18832-4@http.gcc.gnu.org/bugzilla/>
2011-03-17 23:14 ` law at redhat dot com
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=20050423010819.19927.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).