public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Vadim Ogranovich <vograno@arbitrade.com>
To: gdr@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/3552: missing hash function for std::string
Date: Sat, 27 Apr 2002 12:46:00 -0000 [thread overview]
Message-ID: <20020427194605.28006.qmail@sources.redhat.com> (raw)
The following reply was made to PR libstdc++/3552; it has been noted by GNATS.
From: Vadim Ogranovich <vograno@arbitrade.com>
To: "'goswin.brederlow@student.uni-tuebingen.de'"
<goswin.brederlow@student.uni-tuebingen.de>,
"'gcc-gnats@gcc.gnu.org'"
<gcc-gnats@gcc.gnu.org>,
"'gcc-prs@gcc.gnu.org'" <gcc-prs@gcc.gnu.org>,
"'Laurent.Bonnaud@inpg.fr'" <Laurent.Bonnaud@inpg.fr>,
"'87063-quiet@bugs.debian.org'" <87063-quiet@bugs.debian.org>,
"'gcc-bugs@gcc.gnu.org'" <gcc-bugs@gcc.gnu.org>
Cc:
Subject: Re: libstdc++/3552: missing hash function for std::string
Date: Sat, 27 Apr 2002 14:37:52 -0500
Hi, I independently came across this bug. It seems like it was classified as
not a bug with no workaround posted. Is that the case? Thanks, Vadim
P.S. From searching the Web I found that this "not-a-bug" first surfaced in
1998 and has been bugging people since then.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view audit-trail
--------------------------------------------------
DISCLAIMER
This e-mail, and any attachments thereto, is intended only for use by the
addressee(s) named herein and may contain legally privileged and/or
confidential information. If you are not the intended recipient of this
e-mail, you are hereby notified that any dissemination, distribution or
copying of this e-mail, and any attachments thereto, is strictly prohibited.
If you have received this e-mail in error, please immediately notify me and
permanently delete the original and any copy of any e-mail and any printout
thereof.
E-mail transmission cannot be guaranteed to be secure or error-free. The
sender therefore does not accept liability for any errors or omissions in
the contents of this message which arise as a result of e-mail transmission.
NOTICE REGARDING PRIVACY AND CONFIDENTIALITY
Knight Trading Group may, at its discretion, monitor and review the content
of all e-mail communications.
next reply other threads:[~2002-04-27 19:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-27 12:46 Vadim Ogranovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-08 11:46 Phil Edwards
2002-05-08 10:06 Goswin Brederlow
2002-04-29 12:56 Vadim Ogranovich
2002-04-29 12:46 Phil Edwards
2002-04-29 12:16 Phil Edwards
2001-07-03 16:26 Gabriel Dos Reis
2001-07-03 16:18 gdr
2001-07-03 15:26 Matthias Klose
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=20020427194605.28006.qmail@sources.redhat.com \
--to=vograno@arbitrade.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=gdr@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).