public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug regression/19174] wrong code regression or library problem in gcc-4.0-20041226
Date: Tue, 04 Jan 2005 00:03:00 -0000 [thread overview]
Message-ID: <20050104000332.32443.qmail@sourceware.org> (raw)
In-Reply-To: <20041228130233.19174.andre.maute@gmx.de>
------- Additional Comments From rth at gcc dot gnu dot org 2005-01-04 00:03 -------
I'm willing to lay money this is the same problem as PR 19235.
*** This bug has been marked as a duplicate of 19235 ***
--
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution| |DUPLICATE
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19174
next prev parent reply other threads:[~2005-01-04 0:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 13:02 [Bug regression/19174] New: " andre dot maute at gmx dot de
2004-12-28 14:29 ` [Bug regression/19174] " pinskia at gcc dot gnu dot org
2004-12-28 17:21 ` andre dot maute at gmx dot de
2004-12-28 18:03 ` andre dot maute at gmx dot de
2004-12-29 0:42 ` rth at gcc dot gnu dot org
2004-12-29 11:14 ` andre dot maute at gmx dot de
2005-01-01 23:58 ` andre dot maute at gmx dot de
2005-01-02 21:06 ` andre dot maute at gmx dot de
2005-01-02 23:44 ` andre dot maute at gmx dot de
2005-01-04 0:03 ` rth at gcc dot gnu dot org [this message]
2005-01-04 17:46 ` andre dot maute at gmx dot de
2005-01-10 0:00 ` andre dot maute at gmx dot de
2005-01-17 12:28 ` andre dot maute at gmx dot de
2005-01-19 21:22 ` rth at gcc dot gnu dot org
2005-01-20 6:59 ` rth at gcc dot gnu dot org
2005-01-24 10:42 ` andre dot maute at gmx dot de
2005-01-24 13:30 ` [Bug regression/19174] [4.0 Regression] " 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=20050104000332.32443.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).