public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "paolo at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/26127] tr1/hashtable compile errors
Date: Tue, 07 Feb 2006 15:11:00 -0000	[thread overview]
Message-ID: <20060207151115.25733.qmail@sourceware.org> (raw)
In-Reply-To: <bug-26127-1827@http.gcc.gnu.org/bugzilla/>



------- Comment #2 from paolo at gcc dot gnu dot org  2006-02-07 15:11 -------
Subject: Bug 26127

Author: paolo
Date: Tue Feb  7 15:11:10 2006
New Revision: 110697

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=110697
Log:
2006-02-07  Paolo Carlini  <pcarlini@suse.de>   

        * include/tr1/hashtable: Trivial formatting fixes.

2006-02-07  Paolo Carlini  <pcarlini@suse.de>
            Zak Kipling  <zak@transversal.com>

        PR libstdc++/26127
        * include/tr1/hashtable (hashtable<>::key_equal): Define.
        (hashtable<>::bucket, rehash_base<>::max_load_factor): Fix.
        * testsuite/tr1/6_containers/unordered/hashtable/26127.cc: New.

Added:
    trunk/libstdc++-v3/testsuite/tr1/6_containers/unordered/hashtable/26127.cc
Modified:
    trunk/libstdc++-v3/ChangeLog
    trunk/libstdc++-v3/include/tr1/hashtable


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26127


  parent reply	other threads:[~2006-02-07 15:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-06 14:02 [Bug libstdc++/26127] New: " zak at transversal dot com
2006-02-06 14:19 ` [Bug libstdc++/26127] " chris at bubblescope dot net
2006-02-06 14:34 ` pcarlini at suse dot de
2006-02-07 15:11 ` paolo at gcc dot gnu dot org [this message]
2006-02-07 15:11 ` paolo at gcc dot gnu dot org
2006-02-07 15:13 ` pcarlini at suse dot de

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=20060207151115.25733.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).