From: Igor Markov <imarkov@eecs.umich.edu>
To: Andrew Pinski <pinskia@physics.uc.edu>
Cc: gcc@gcc.gnu.org
Subject: Re: 3.1.1: hash_map don't work
Date: Mon, 19 Aug 2002 18:53:00 -0000 [thread overview]
Message-ID: <3D61A120.9060703@eecs.umich.edu> (raw)
In-Reply-To: <D9B4BF2C-B3DD-11D6-89AF-000393122612@physics.uc.edu>
Ok, thanks -- that worked.
Is there a document with such gotchas?
For gcc developers:
If at all possible, it would be nice for g++
to be more intelligent with error diagnostics
in such cases. Having moved things around,
it would make sense to add some code to intercept
obvious error messages and add clarifications.
Igor
Andrew Pinski wrote:
next prev parent reply other threads:[~2002-08-19 18:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-19 18:22 Igor Markov
2002-08-19 18:40 ` Andrew Pinski
2002-08-19 18:53 ` Igor Markov [this message]
2002-08-19 19:19 ` Phil Edwards
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=3D61A120.9060703@eecs.umich.edu \
--to=imarkov@eecs.umich.edu \
--cc=gcc@gcc.gnu.org \
--cc=pinskia@physics.uc.edu \
/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).