public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bkoz@gcc.gnu.org
To: bkoz@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	gdr@codesourcery.com, kenny.simpson@gs.com,
	theonetruekenny@yahoo.com
Subject: Re: libstdc++/3139: DR 184: numeric_limits<bool> problems
Date: Thu, 28 Mar 2002 15:11:00 -0000	[thread overview]
Message-ID: <20020328231145.26426.qmail@sources.redhat.com> (raw)

Synopsis: DR 184: numeric_limits<bool> problems

State-Changed-From-To: analyzed->feedback
State-Changed-By: bkoz
State-Changed-When: Thu Mar 28 15:11:44 2002
State-Changed-Why:
    
    AAaaaagh. Gaby, this is is off. Can you confirm this is ok?
    
    
    2002-03-28  Benjamin Kosnik  <bkoz@redhat.com>
    
    	As per DR 184, libstdc++/3139
    	* include/std/std_limits.h (__glibcpp_bool_digits): Change to 1.
    	(numeric_limits<bool>::is_iec559): False.
    	(numeric_limits<bool>::is_modulo): False.	
    
    Index: std_limits.h
    ===================================================================
    RCS file: /cvs/gcc/gcc/libstdc++-v3/include/std/std_limits.h,v
    retrieving revision 1.4
    diff -c -p -r1.4 std_limits.h
    *** std_limits.h	2002/03/08 17:59:12	1.4
    --- std_limits.h	2002/03/28 23:10:46
    ***************
    *** 233,243 ****
      // bool-specific hooks:
      //     __glibcpp_bool_digits  __glibcpp_int_traps __glibcpp_long_traps
      
    - // This is actually CHAR_BITS because the new ABI says a bool
    - // is one (1) byte wide.
    - 
      #ifndef __glibcpp_bool_digits
    ! #define __glibcpp_bool_digits __glibcpp_char_bits
      #endif
      
      // char.
    --- 233,240 ----
      // bool-specific hooks:
      //     __glibcpp_bool_digits  __glibcpp_int_traps __glibcpp_long_traps
      
      #ifndef __glibcpp_bool_digits
    ! #define __glibcpp_bool_digits 1
      #endif
      
      // char.
    *************** namespace std
    *** 996,1004 ****
            static bool denorm_min() throw()
            { return false; }
      
    !       static const bool is_iec559 = true;
            static const bool is_bounded = true;
    !       static const bool is_modulo = true;
      
            // It is not clear what it means for a boolean type to trap.
            // This is a DR on the LWG issue list.  Here, I use integer
    --- 993,1001 ----
            static bool denorm_min() throw()
            { return false; }
      
    !       static const bool is_iec559 = false;
            static const bool is_bounded = true;
    !       static const bool is_modulo = false;
      
            // It is not clear what it means for a boolean type to trap.
            // This is a DR on the LWG issue list.  Here, I use integer

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=3139


             reply	other threads:[~2002-03-28 23:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-28 15:11 bkoz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-08  4:06 Gabriel Dos Reis
2002-04-03 21:34 bkoz
2001-06-13  9:57 bkoz
2001-06-12 13:59 bkoz
2001-06-12  9:56 theonetruekenny

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=20020328231145.26426.qmail@sources.redhat.com \
    --to=bkoz@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=gdr@codesourcery.com \
    --cc=kenny.simpson@gs.com \
    --cc=theonetruekenny@yahoo.com \
    /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).