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 c/19937] [4.0 regression] Wrong loop exit
Date: Sun, 13 Feb 2005 22:55:00 -0000 [thread overview]
Message-ID: <20050213162514.18434.qmail@sourceware.org> (raw)
In-Reply-To: <20050213162215.19937.schwab@suse.de>
------- Additional Comments From pinskia at gcc dot gnu dot org 2005-02-13 16:25 -------
Confirmed, looking for where it is miscompiled.
--
What |Removed |Added
----------------------------------------------------------------------------
CC| |pinskia at gcc dot gnu dot
| |org
Status|UNCONFIRMED |NEW
Ever Confirmed| |1
Last reconfirmed|0000-00-00 00:00:00 |2005-02-13 16:25:13
date| |
Target Milestone|--- |4.0.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19937
next prev parent reply other threads:[~2005-02-13 16:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-13 22:20 [Bug c/19937] New: " schwab at suse dot de
2005-02-13 22:55 ` pinskia at gcc dot gnu dot org [this message]
2005-02-13 23:03 ` [Bug tree-optimization/19937] " pinskia at gcc dot gnu dot org
2005-02-13 23:44 ` pinskia at gcc dot gnu dot org
2005-02-14 2:42 ` schwab at suse dot de
2005-02-14 5:16 ` rakdver at gcc dot gnu dot org
2005-02-14 10:22 ` rakdver at gcc dot gnu dot org
2005-02-14 15:03 ` rakdver at atrey dot karlin dot mff dot cuni dot cz
2005-02-14 15:03 ` schlie at comcast dot net
2005-02-18 14:53 ` pinskia at gcc dot gnu dot org
2005-02-18 15:55 ` [Bug tree-optimization/19937] [4.0 regression] Wrong loop exit (causes binutils to fail) schlie at comcast dot net
2005-02-20 22:24 ` pinskia at gcc dot gnu dot org
2005-02-23 16:19 ` jakub at gcc dot gnu dot org
2005-02-25 16:55 ` cvs-commit at gcc dot gnu dot org
2005-02-25 16:56 ` rakdver at gcc dot gnu dot org
2005-02-25 17:04 ` pinskia at gcc dot gnu dot org
2005-02-25 18:14 ` pinskia at gcc dot gnu dot org
2005-02-26 0:02 ` cvs-commit at gcc dot gnu dot org
2005-02-26 0:16 ` rakdver 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=20050213162514.18434.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).