public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: a.keese@tu-bs.de
To: gcc-gnats@gcc.gnu.org
Subject: c++/7820: Compiler bails out with internal error 373
Date: Tue, 03 Sep 2002 15:06:00 -0000 [thread overview]
Message-ID: <20020903215816.1921.qmail@sources.redhat.com> (raw)
>Number: 7820
>Category: c++
>Synopsis: Compiler bails out with internal error 373
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Tue Sep 03 15:06:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: a.keese@tu-bs.de
>Release: gcc version 2.95.3 20010315 (SuSE)
>Organization:
>Environment:
SuSE-Linux 8.0, standard installation
/usr/lib/gcc-lib/i486-suse-linux/2.95.3/specs:
gcc version 2.95.3 20010315 (SuSE)
>Description:
The compilation stops with the error:
test_adt_io.cc: In function `int main(int, char **)':
test_adt_io.cc:7: Internal compiler error 373.
test_adt_io.cc:7: Please submit a full bug report.
test_adt_io.cc:7: See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.
>How-To-Repeat:
Just say
g++ test_adt_io.cc adt_io.cc
>Fix:
?
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/x-gunzip; name="bug_template.tar.gz"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="bug_template.tar.gz"
H4sIADEvdT0AA+2XUW/aMBDHecWf4gTSGtBGEyBhKghpUjutD9MmlT1MmhS5wQGvwY5iZ1XV8d3n
OKEFCoW0gu7BPwlycXL2nWX/z8Fj6VPeCoLK4bAd2/a6dsW2257ndtRV0XPyq207blfZPbfjttte
t6fec5yuZ1fAPmBMD6RC4gSggm8IEWT7e7c0OUY4x6ZOWRClYwI1nK+EaQ09tA0on2FG49Z0iBDD
MyJiHBDAN6mkEdwjBBouZELw7B0IIn2eyjiVfsiTGVaXiGNpPbzARUO5VSEhMk2YuoXBIPOiXIQR
nggLlHV2FpFQwt/cFlN+G3PKJDQAVatquNwlTkhABeXM6q4+CGkUWSf2SWO58db62OhXdYOiiHuO
9shAjUwmJCmdQ0In0/WY89BgPTS30X+MKDckmcURlmQwfCa2gYptuDuwzQm9cMiIs8mxxxzz9Doi
5UfVi++FY2rf1w85R2+9wXew2PWHHGOX/vfa7XX977Q7Rv+PQZ2GbExC8NUq8GWCqRT+1PdRXTVS
Rp60oyDCQix2Th+h02YTQRPg13VCVT+fUxYoKWQCRBrHPJGUTWBCGEloAPleAR7CGEus3E63lhXV
7SvQG7D4hysidRRySkArdBYAZoscQG1d/SyL6YO8i8my92s4XWRSBFJM0UKAxqCLa6rsLAIOYyrU
gzvg179JIHWY+Wx/Hf38fgGcQdFRwWMOLfghCFAJEb0hKhkqzlamAAI19Zli5XOsquo2kdUvnWs7
MwkbR/39O8kKEuSVDbNLVbNhrZNTtKzAS9kNgbIoW3DbNfkZMda9z1f6Llc4+/v7Pq2AJZw3lbIS
7huqkvZGc7UT62qeaViy4EgipI8P+xGwQ/9tz3s8/3uOsp2263hG/4/B8lm/0BJ12N/0VYCyM/gM
U2ZlBk4mwXsIpjhpNrObP+qke18crRc6URtdXI38T+cj//JbbUUISsmRldsNt2UvOkHVZ53zbaK1
x9J2Cd8lCcsSbbh7+mlZKPwye29HPYd5sLUvOIr46lRlv0Ln7P7/f540GAwGg8FgMBgMBoPBYDAY
DAaDwfD2/AMNsE5DACgAAA==
next reply other threads:[~2002-09-03 22:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-03 15:06 a.keese [this message]
2002-09-09 12:09 paolo
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=20020903215816.1921.qmail@sources.redhat.com \
--to=a.keese@tu-bs.de \
--cc=gcc-gnats@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).