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/14341] Missed comparision optimization (jump threading related)
Date: Wed, 22 Dec 2004 05:33:00 -0000 [thread overview]
Message-ID: <20041222053304.1159.qmail@sourceware.org> (raw)
In-Reply-To: <20040229062941.14341.pinskia@gcc.gnu.org>
------- Additional Comments From pinskia at gcc dot gnu dot org 2004-12-22 05:33 -------
(In reply to comment #9)
> The first two testcases seem to be OK. All calls to f are f(1).
>
> The last testcase is probably not what Andrew had in mind.
> Specifically, "i" in the innermost scope isn't initialized.
>
> Andrew, can you confirm (and close if you think these are fixed)?
It is not fixed for me on PPC:
cmpw cr7,r30,r28
crnot 30,29
mfcr r3
rlwinm r3,r3,31,1
bl L_f$stub
r3 is where the first argrument is stored.
but you are right about the last testcase being wrong.
--
What |Removed |Added
----------------------------------------------------------------------------
GCC target triplet| |powerpc-darwin
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14341
next prev parent reply other threads:[~2004-12-22 5:33 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 6:29 [Bug optimization/14341] New: Missed optimization pinskia at gcc dot gnu dot org
2004-02-29 6:37 ` [Bug optimization/14341] Missed comparision optimization (jump threading related) pinskia at gcc dot gnu dot org
2004-02-29 14:20 ` steven at gcc dot gnu dot org
2004-02-29 16:15 ` pinskia at gcc dot gnu dot org
2004-03-01 4:28 ` law at redhat dot com
2004-03-01 14:37 ` law at gcc dot gnu dot org
2004-03-07 4:51 ` pinskia at gcc dot gnu dot org
2004-03-07 4:52 ` pinskia at gcc dot gnu dot org
2004-05-13 20:26 ` [Bug tree-optimization/14341] " pinskia at gcc dot gnu dot org
2004-05-24 16:51 ` pinskia at gcc dot gnu dot org
2004-12-22 5:23 ` kazu at cs dot umass dot edu
2004-12-22 5:33 ` pinskia at gcc dot gnu dot org [this message]
2004-12-23 18:32 ` law at redhat dot com
2005-01-31 14:03 ` kazu at cs dot umass dot edu
2005-01-31 14:47 ` pinskia at gcc dot gnu dot org
2005-01-31 15:25 ` [Bug tree-optimization/14341] Missed comparison " kazu at cs dot umass dot edu
2005-01-31 15:33 ` pinskia at gcc dot gnu dot org
2005-01-31 15:43 ` kazu at cs dot umass dot edu
2005-05-07 19:30 ` [Bug tree-optimization/14341] Missed comparison optimization (VRP) pinskia at gcc dot gnu dot org
2005-06-02 2:58 ` cvs-commit at gcc dot gnu dot org
2005-06-02 3:03 ` dnovillo at gcc dot gnu dot org
2005-06-02 18:44 ` pinskia at gcc dot gnu dot org
2005-09-10 18:11 ` 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=20041222053304.1159.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).