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/19581] Missed store monition on the tree level
Date: Sun, 23 Jan 2005 20:00:00 -0000 [thread overview]
Message-ID: <20050123195959.14750.qmail@sourceware.org> (raw)
In-Reply-To: <20050123014322.19581.pinskia@gcc.gnu.org>
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-01-23 19:59 -------
(In reply to comment #5)
> GCSE store motion does catch this. But it is disabled for GCC 4.0 because
> it is buggy and does not really work well in most cases.
Yes but we don't catch in 3.4.0 so that means GCSE store motion did not catch it since GCSE store
motion was only disabled for 4.0.0 but was enabled after the rewrite for 3.4.0.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19581
next prev parent reply other threads:[~2005-01-23 20:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-23 1:43 [Bug tree-optimization/19581] New: Missed store monition on the tree level (on PPC in general) pinskia at gcc dot gnu dot org
2005-01-23 1:45 ` [Bug tree-optimization/19581] " pinskia at gcc dot gnu dot org
2005-01-23 1:47 ` dberlin at gcc dot gnu dot org
2005-01-23 19:27 ` steven at gcc dot gnu dot org
2005-01-23 19:30 ` [Bug tree-optimization/19581] Missed store monition on the tree level steven at gcc dot gnu dot org
2005-01-23 19:44 ` rakdver at gcc dot gnu dot org
2005-01-23 19:53 ` steven at gcc dot gnu dot org
2005-01-23 20:00 ` pinskia at gcc dot gnu dot org [this message]
2005-01-23 20:01 ` rakdver at gcc dot gnu dot org
2005-07-26 13:21 ` [Bug tree-optimization/19581] Missed store motion " dberlin at gcc dot gnu dot org
2005-07-26 13:59 ` rguenth 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=20050123195959.14750.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).