public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Craig Rodrigues <rodrigc@mediaone.net>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: c++/3391
Date: Sat, 08 Sep 2001 11:36:00 -0000 [thread overview]
Message-ID: <20010908183601.7925.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR c++/3391; it has been noted by GNATS.
From: Craig Rodrigues <rodrigc@mediaone.net>
To: desarrollo@dedalo-ing.com, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org,
rafa@dedalo-ing.com, gcc-bugs@gcc.gnu.org, nobody@gcc.gnu.org
Cc:
Subject: Re: c++/3391
Date: Sat, 08 Sep 2001 14:31:20 -0400
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=3391&database=gcc
With gcc 3.0.2 2020010907 (prerelease), compiled with --enable-checking,
I get the following
error message:
/home/rafa/src/GCC-3.0/mpcl/include/mpcl/smart_pointer.hh:321:
Tree check: expected tree_vec, have tree_list in dfs_walk_real, at
cp/search.c:1850
--
Craig Rodrigues
rodrigc@mediaone.net
next reply other threads:[~2001-09-08 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-08 11:36 Craig Rodrigues [this message]
2001-09-20 1:06 c++/3391 Rafael Jesus Alcantara Perez
2001-09-20 8:16 c++/3391 Reichelt
2001-10-12 2:26 c++/3391 Rafael Jesus Alcantara Perez
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=20010908183601.7925.qmail@sourceware.cygnus.com \
--to=rodrigc@mediaone.net \
--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).