public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/8971: [Tru64 4.0] virtual memory exhausted: Not enough space
Date: Wed, 14 May 2003 10:06:00 -0000 [thread overview]
Message-ID: <20030514100601.17430.qmail@sources.redhat.com> (raw)
The following reply was made to PR bootstrap/8971; it has been noted by GNATS.
From: Dara Hazeghi <dhazeghi@yahoo.com>
To: iknopf@csc-dd.de, gcc-gnats@gcc.gnu.org, nobody@gcc.gnu.org
Cc:
Subject: Re: bootstrap/8971: [Tru64 4.0] virtual memory exhausted: Not enough space
Date: Wed, 14 May 2003 02:58:04 -0700
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-
trail&database=gcc&pr=8971
Hello,
would it be possible to determine whether this problem still occurs on
gcc 3.3? No guarantees, but someone might have fixed your bug :-)
Thanks,
Dara
next reply other threads:[~2003-05-14 10:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-14 10:06 Dara Hazeghi [this message]
2003-05-14 10:49 giovannibajo
2003-05-17 9:16 Dara Hazeghi
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=20030514100601.17430.qmail@sources.redhat.com \
--to=dhazeghi@yahoo.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).