public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: harald.soleng@nr.no
To: gcc-gnats@gcc.gnu.org
Subject: c++/5633: bool is too big
Date: Fri, 08 Feb 2002 03:06:00 -0000	[thread overview]
Message-ID: <20020208105639.17312.qmail@sources.redhat.com> (raw)


>Number:         5633
>Category:       c++
>Synopsis:       bool is too big
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Fri Feb 08 03:06:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     harald.soleng@nr.no
>Release:        gcc-2.95.3
>Organization:
>Environment:
sparc-solaris
>Description:
The bool variable takes up 4 bytes or 32 bits where 1 bit 
is sufficient.

For large bool arrays this is a waste of memory.
Why not try to reduce this waste of memory?
>How-To-Repeat:

>Fix:

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


             reply	other threads:[~2002-02-08 11:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-08  3:06 harald.soleng [this message]
2002-02-08  3:16 nathan
2002-02-20  8:16 Gabriel Dos Reis

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=20020208105639.17312.qmail@sources.redhat.com \
    --to=harald.soleng@nr.no \
    --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).