From: Geert Bosch <bosch@gnat.com>
To: guerby@acm.org
Cc: gcc@gcc.gnu.org
Subject: Re: [Ada] stage2 failure on i686-pc-linux-gnu
Date: Sat, 20 Oct 2001 12:20:00 -0000 [thread overview]
Message-ID: <Pine.GSO.4.10.10110201518420.22265-100000@nile.gnat.com> (raw)
In-Reply-To: <200110201753.f9KHrXH15481@ulmo.localdomain>
On Sat, 20 Oct 2001 guerby@acm.org wrote:
It was working yesterday. Same result with GNAT 3.13p from ALT and ACT, this
is on Mandrake 8.1.
Procedural question: should this kind of report go to gcc@gcc.gnu.org, and/or
be filed as bootstrap in GNATS?
I'd say, send it to gcc@gcc.gnu.org, and only file it as bug if it doesn't
get fixed in a week or so.
-Geert
next prev parent reply other threads:[~2001-10-20 12:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-20 10:59 guerby
2001-10-20 12:20 ` Geert Bosch [this message]
2001-10-22 12:16 ` guerby
2001-10-22 13:43 ` Geert Bosch
2001-10-22 15:16 ` Richard Henderson
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=Pine.GSO.4.10.10110201518420.22265-100000@nile.gnat.com \
--to=bosch@gnat.com \
--cc=gcc@gcc.gnu.org \
--cc=guerby@acm.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).