public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
* [gcc r11-6766] libstdc++: Fix narrow char test to use stringbuf not wstringbuf
@ 2021-01-18 12:50 Jonathan Wakely
  0 siblings, 0 replies; only message in thread
From: Jonathan Wakely @ 2021-01-18 12:50 UTC (permalink / raw)
  To: gcc-cvs, libstdc++-cvs

https://gcc.gnu.org/g:a81d2f1e414836549b909f2de927b6ae10e8b156

commit r11-6766-ga81d2f1e414836549b909f2de927b6ae10e8b156
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Mon Jan 18 12:44:27 2021 +0000

    libstdc++: Fix narrow char test to use stringbuf not wstringbuf
    
    This seems to be a copy & paste error.
    
    libstdc++-v3/ChangeLog:
    
            * testsuite/27_io/basic_stringstream/cons/char/1.cc: Use
            stringbuf not wstringbuf.

Diff:
---
 libstdc++-v3/testsuite/27_io/basic_stringstream/cons/char/1.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libstdc++-v3/testsuite/27_io/basic_stringstream/cons/char/1.cc b/libstdc++-v3/testsuite/27_io/basic_stringstream/cons/char/1.cc
index 31130ee5c95..7cb9f34ca04 100644
--- a/libstdc++-v3/testsuite/27_io/basic_stringstream/cons/char/1.cc
+++ b/libstdc++-v3/testsuite/27_io/basic_stringstream/cons/char/1.cc
@@ -107,7 +107,7 @@ test04()
   sstream ss3(std::string(str), std::ios::out, a);
   VERIFY( ss3.str() == cstr );
   VERIFY( bool(ss3 << 1) );
-  VERIFY( ss3.get() == std::wstringbuf::traits_type::eof() );
+  VERIFY( ss3.get() == std::stringbuf::traits_type::eof() );
 }
 
 int


^ permalink raw reply	[flat|nested] only message in thread
only message in thread, other threads:[~2021-01-18 12:50 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-01-18 12:50 [gcc r11-6766] libstdc++: Fix narrow char test to use stringbuf not wstringbuf Jonathan Wakely

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).