public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: pme@gcc.gnu.org
To: gcc-gnats@gcc.gnu.org
Subject: libstdc++/6282: bitset<0> results in nonsense behavior
Date: Fri, 12 Apr 2002 13:16:00 -0000	[thread overview]
Message-ID: <20020412200824.18100.qmail@sources.redhat.com> (raw)


>Number:         6282
>Category:       libstdc++
>Synopsis:       bitset<0> results in nonsense behavior
>Confidential:   no
>Severity:       critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Apr 12 13:16:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Phil Edwards
>Release:        3.x
>Organization:
>Environment:
All.  (Not platform-specific code.)
>Description:
Creating a std::bitset instance of zero size still stores
a word's worth of data.

Consider

  std::bitset<1>  x(555555);
  int i = x.count();

Only the least significant bit from 555555 will be stored,
and i will correctly be set to 1 (the count of "on" bits
in x).  But if x is defined as

  std::bitset<0>  x(555555);

then there are still sizeof(unsigned long) bits being
stored and initialized, and x.count() returns 9 instead of
the more correct 0.  Other bitset member functions return
likewise silly results.


The base class for bitset is not taking into account the
empty case.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-04-12 20:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-12 13:16 pme [this message]
2002-04-12 13:28 pme
2002-05-24 11:22 pme

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=20020412200824.18100.qmail@sources.redhat.com \
    --to=pme@gcc.gnu.org \
    --cc=gcc-gnats@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).