From: Igor Markov <imarkov@eecs.umich.edu>
To: gcc@gcc.gnu.org
Subject: 3.1.1: hash_map don't work
Date: Mon, 19 Aug 2002 18:22:00 -0000 [thread overview]
Message-ID: <3D6199C4.7070303@eecs.umich.edu> (raw)
Greetings,
The following code gets compiled w/o problem by g++ 3.0.4,
but doesn't with g++ 3.1.1
#include <ext/hash_map>
using std::hash_map;
main() {}
/n/gagarin/z/imarkov/devel/ /usr/bin/g++-3.0 test.cxx
/n/gagarin/z/imarkov/devel/ /usr/bin/g++-3.1 test.cxx
test.cxx:4: `hash_map' not declared
/n/gagarin/z/imarkov/devel/ uname -a
Linux gagarin.eecs.umich.edu 2.4.18 #6 SMP Mon Jul 15 12:00:46 EDT 2002
i686 unknown
/n/gagarin/z/imarkov/devel/
Can anyone reproduce this?
If not, I should bother my sysadmin, who installed both 3.0 and 3.1.
Otherwise, is it a bug or a feature?
Should I expect 3.2 to behave the same way as 3.1 or as 3.0 ?
thanks,
Igor
--
Igor L. Markov (734) 936-7829 EECS 2211
http://www.eecs.umich.edu/~imarkov
next reply other threads:[~2002-08-19 18:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-19 18:22 Igor Markov [this message]
2002-08-19 18:40 ` Andrew Pinski
2002-08-19 18:53 ` Igor Markov
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=3D6199C4.7070303@eecs.umich.edu \
--to=imarkov@eecs.umich.edu \
--cc=gcc@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).