public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "igodard at pacbell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/15154] New: Lib doesn't provide implementations for some bitset extensions
Date: Mon, 26 Apr 2004 19:56:00 -0000	[thread overview]
Message-ID: <20040426195354.15154.igodard@pacbell.net> (raw)

Gnu libstdc++ "bitset" supports extensions inherited from SGI, including the pseudo-iterators _Find_first and _Find_next. The library provides inplementations for these in the general case. However, bitset is specialized for the case where the entire set fits in a machine word (i.e. _base_bitset<1>) and the source does *not* provide _Find_first and _Find_next for those.

Thus:
#include

-- 
           Summary: Lib doesn't provide implementations for some bitset
                    extensions
           Product: gcc
           Version: 3.3.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: libstdc++
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: igodard at pacbell dot net
                CC: gcc-bugs at gcc dot gnu dot org


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


             reply	other threads:[~2004-04-26 19:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-26 19:56 igodard at pacbell dot net [this message]
2004-04-26 20:40 ` [Bug libstdc++/15154] " pinskia at gcc dot gnu dot org
2004-04-26 20:42 ` igodard at pacbell dot net
2004-04-26 22:05 ` [Bug libstdc++/15154] [3.3 Regression] " pinskia at gcc dot gnu dot org
2004-05-01 23:40 ` gdr at gcc dot gnu dot org
2004-05-01 23:46 ` gdr at gcc dot gnu dot org
2004-06-11 22:22 ` pinskia at gcc dot gnu dot org
2004-09-28 13:38 ` gdr at gcc dot gnu dot org
2005-04-30 13:40 ` gdr at gcc dot gnu dot org

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=20040426195354.15154.igodard@pacbell.net \
    --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).