public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r13-2999] libstdc++: Remove <sstream> dependency from std::bitset::to_ulong() test
Date: Fri, 30 Sep 2022 20:57:01 +0000 (GMT)	[thread overview]
Message-ID: <20220930205702.2EB3238582B0@sourceware.org> (raw)

https://gcc.gnu.org/g:789ddef1cf5a906802f61b2c494a86b80489f2e5

commit r13-2999-g789ddef1cf5a906802f61b2c494a86b80489f2e5
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Fri Sep 30 15:54:19 2022 +0100

    libstdc++: Remove <sstream> dependency from std::bitset::to_ulong() test
    
    There's no need to use a stringstream to test the to_ulong() member.
    This will allow the test to be used in freestanding mode.
    
    libstdc++-v3/ChangeLog:
    
            * testsuite/20_util/bitset/access/to_ulong.cc: Construct bitset
            from binary literal instead of using stringstream.

Diff:
---
 libstdc++-v3/testsuite/20_util/bitset/access/to_ulong.cc | 13 +------------
 1 file changed, 1 insertion(+), 12 deletions(-)

diff --git a/libstdc++-v3/testsuite/20_util/bitset/access/to_ulong.cc b/libstdc++-v3/testsuite/20_util/bitset/access/to_ulong.cc
index 8163701e342..edc021c209c 100644
--- a/libstdc++-v3/testsuite/20_util/bitset/access/to_ulong.cc
+++ b/libstdc++-v3/testsuite/20_util/bitset/access/to_ulong.cc
@@ -20,22 +20,11 @@
 // 23.3.5.2 bitset members
 
 #include <bitset>
-#include <stdexcept>
-#include <sstream>
 #include <testsuite_hooks.h>
 
 void test03()
 {
-  std::bitset<5>      b;
-  std::stringstream   ss("101");
-  ss.exceptions(std::ios_base::eofbit);
-
-  try
-  {
-    ss >> b;
-  }
-  catch (std::exception&) { }
-
+  std::bitset<5>      b(0b101);
   VERIFY( b.to_ulong() == 5 );
 }

                 reply	other threads:[~2022-09-30 20:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220930205702.2EB3238582B0@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@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).