public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/13750] [3.4/3.5 Regression] Ada bootstrap failure on Tru64 UNIX: b_gnat[1b].o comparison failure
Date: Thu, 05 Feb 2004 21:19:00 -0000 [thread overview]
Message-ID: <20040205211944.31873.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040119221419.13750.ro@techfak.uni-bielefeld.de>
------- Additional Comments From mark at codesourcery dot com 2004-02-05 21:19 -------
Subject: Re: [3.4/3.5 Regression] Ada bootstrap failure
on Tru64 UNIX: b_gnat[1b].o comparison failure
ro at techfak dot uni-bielefeld dot de wrote:
>------- Additional Comments From ro at techfak dot uni-bielefeld dot de 2004-02-05 19:55 -------
>Subject: Re: [3.4/3.5 Regression] Ada bootstrap failure on Tru64 UNIX: b_gnat[1b].o comparison failure
>
>I intended to revert the patch for PR pch/13361 that caused this
>regression, both for the 3.4 branch and mainline, since nobody was prepared
>to fix it. Ok?
>
Why isn't Geoff going to fix it?
It looks like reverting that patch would break PCH for C++, if I'm
reading it correctly.
If the patch causes a new problem, then it's Geoff responsibility to fix it.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13750
next prev parent reply other threads:[~2004-02-05 21:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-19 22:14 [Bug ada/13750] New: " gcc-bugzilla at gcc dot gnu dot org
2004-01-19 22:16 ` [Bug ada/13750] " ro at gcc dot gnu dot org
2004-01-20 3:45 ` [Bug ada/13750] [3.5 Regression] " pinskia at gcc dot gnu dot org
2004-01-20 15:21 ` charlet at gcc dot gnu dot org
2004-01-20 23:12 ` ro at techfak dot uni-bielefeld dot de
2004-01-20 23:23 ` [Bug ada/13750] [3.4/3.5 " pinskia at gcc dot gnu dot org
2004-01-21 17:50 ` ro at techfak dot uni-bielefeld dot de
2004-01-21 17:56 ` [Bug middle-end/13750] " charlet at gcc dot gnu dot org
2004-01-21 21:08 ` geoffk at gcc dot gnu dot org
2004-01-21 21:14 ` charlet at act-europe dot fr
2004-01-22 11:27 ` charlet at gcc dot gnu dot org
2004-01-22 14:13 ` charlet at gcc dot gnu dot org
2004-01-22 19:29 ` [Bug target/13750] " geoffk at gcc dot gnu dot org
2004-01-23 20:34 ` ro at gcc dot gnu dot org
2004-01-23 20:37 ` pinskia at gcc dot gnu dot org
2004-01-23 22:39 ` ro at techfak dot uni-bielefeld dot de
2004-02-05 19:50 ` mmitchel at gcc dot gnu dot org
2004-02-05 19:55 ` ro at techfak dot uni-bielefeld dot de
2004-02-05 21:19 ` mark at codesourcery dot com [this message]
2004-02-05 21:32 ` ro at techfak dot uni-bielefeld dot de
2004-02-05 21:42 ` mark at codesourcery dot com
2004-02-05 21:56 ` cvs-commit at gcc dot gnu dot org
2004-02-05 22:01 ` cvs-commit at gcc dot gnu dot org
2004-02-05 22:02 ` geoffk at gcc dot gnu dot org
2004-02-05 22:03 ` ro at techfak dot uni-bielefeld dot de
2004-02-05 22:08 ` ro at techfak dot uni-bielefeld dot de
2004-02-06 2:47 ` pinskia at gcc dot gnu dot org
2004-04-05 17:27 ` 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=20040205211944.31873.qmail@sources.redhat.com \
--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).