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/20188] [4.0 Regression] asm and memory operands does not add a V_MAY_DEF
Date: Fri, 25 Feb 2005 21:12:00 -0000 [thread overview]
Message-ID: <20050225151708.15097.qmail@sourceware.org> (raw)
In-Reply-To: <20050224132918.20188.pluto@pld-linux.org>
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-25 15:17 -------
(In reply to comment #13)
> (In reply to comment #12)
> This is the right fix. Could you bootstrap and test it? A test case for this
> would need a dg-scan test for two 'if ()' statements (i.e., we should not value
> number the second if() out).
Will do.
-- Pinski
--
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |pinskia at gcc dot gnu dot
|dot org |org
Status|NEW |ASSIGNED
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20188
next prev parent reply other threads:[~2005-02-25 15:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-24 16:14 [Bug other/20188] New: glibc-2.3.4 misscompilation pluto at pld-linux dot org
2005-02-24 16:14 ` [Bug other/20188] " pluto at pld-linux dot org
2005-02-24 17:25 ` pinskia at gcc dot gnu dot org
2005-02-24 23:49 ` pluto at pld-linux dot org
2005-02-25 0:29 ` pluto at pld-linux dot org
2005-02-25 1:00 ` [Bug middle-end/20188] [4.0 Regression] " pinskia at gcc dot gnu dot org
2005-02-25 1:12 ` [Bug tree-optimization/20188] " pinskia at gcc dot gnu dot org
2005-02-25 1:38 ` pinskia at gcc dot gnu dot org
2005-02-25 7:13 ` pluto at pld-linux dot org
2005-02-25 12:37 ` pinskia at gcc dot gnu dot org
2005-02-25 15:17 ` [Bug tree-optimization/20188] [4.0 Regression] asm and memory operands does not add a V_MAY_DEF pinskia at gcc dot gnu dot org
2005-02-25 15:30 ` pinskia at gcc dot gnu dot org
2005-02-25 15:43 ` pinskia at gcc dot gnu dot org
2005-02-25 15:49 ` pinskia at gcc dot gnu dot org
2005-02-25 20:42 ` dnovillo at gcc dot gnu dot org
2005-02-25 21:12 ` pinskia at gcc dot gnu dot org [this message]
2005-02-25 21:19 ` pinskia at gcc dot gnu dot org
2005-02-27 5:31 ` [Bug tree-optimization/20188] [4.0/4.1 " cvs-commit at gcc dot gnu dot org
2005-02-27 5:32 ` cvs-commit at gcc dot gnu dot org
2005-02-27 5:40 ` pinskia at gcc dot gnu dot org
2005-02-27 14:59 ` danglin at gcc dot gnu dot org
2005-02-27 15:50 ` 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=20050225151708.15097.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).