public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/20100] [4.0 regression] static call incorrectly judged constant, moved out of loop
Date: Sun, 20 Feb 2005 16:38:00 -0000 [thread overview]
Message-ID: <20050220085519.25424.qmail@sourceware.org> (raw)
In-Reply-To: <20050220030431.20100.hp@gcc.gnu.org>
------- Additional Comments From hp at gcc dot gnu dot org 2005-02-20 08:55 -------
I don't really understand this part of comment #4 which apparently is the reason
for relabelling this PR as rtl-optimization: "Currently in 4.0.x, pure/const is
found by the rtl and not by tree wise". See the bug description, where I
explicitly state that the invalid transformation is done already when RTL is
generated (that is, as evident in the first dump).
Though looking in GCC, it seems that indeed RTL is responsible for finding
const and pure code. But that would mean that there's a bug in the RTL-dumping
framework: that it isn't the *initial* RTL that is dumped.
I think I'll have a look so I assign myself this PR.
The bug is still present with LAST_UPDATED "Sun Feb 20 07:53:10 UTC 2005"
so the change referred to apparently doesn't handle this bug even though the
PR and changed code seems related.
--
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |hp at gcc dot gnu dot org
|dot org |
Status|UNCONFIRMED |ASSIGNED
Ever Confirmed| |1
Last reconfirmed|0000-00-00 00:00:00 |2005-02-20 08:55:18
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20100
next prev parent reply other threads:[~2005-02-20 8:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 15:15 [Bug tree-optimization/20100] New: " hp at gcc dot gnu dot org
2005-02-20 15:21 ` [Bug tree-optimization/20100] " hp at gcc dot gnu dot org
2005-02-20 15:21 ` hp at gcc dot gnu dot org
2005-02-20 15:24 ` hp at gcc dot gnu dot org
2005-02-20 15:37 ` [Bug rtl-optimization/20100] " pinskia at gcc dot gnu dot org
2005-02-20 16:38 ` hp at gcc dot gnu dot org [this message]
2005-02-20 22:30 ` [Bug tree-optimization/20100] " pinskia at gcc dot gnu dot org
2005-02-20 22:32 ` pinskia at gcc dot gnu dot org
2005-02-20 22:33 ` pinskia at gcc dot gnu dot org
2005-02-21 2:21 ` [Bug tree-optimization/20100] [4.0 Regression] LIM is pulling out a pure function even though there is something which can modify global memory hp at gcc dot gnu dot org
2005-02-21 2:37 ` pinskia at gcc dot gnu dot org
2005-02-21 15:00 ` pinskia at gcc dot gnu dot org
2005-02-21 16:16 ` dnovillo at gcc dot gnu dot org
2005-02-23 12:50 ` cvs-commit at gcc dot gnu dot org
2005-02-23 15:21 ` steven at gcc dot gnu dot org
2005-02-23 15:29 ` steven at gcc dot gnu dot org
2005-02-24 12:14 ` cvs-commit 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=20050220085519.25424.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).