public inbox for libstdc++-cvs@sourceware.org help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org Subject: [gcc(refs/users/aoliva/heads/testme)] Split wchars tests from the normal variant Date: Fri, 1 Jan 2021 01:29:15 +0000 (GMT) [thread overview] Message-ID: <20210101012915.F05B43857815@sourceware.org> (raw) https://gcc.gnu.org/g:df941d9e7491c782210dfb2bbb11ee4bf1e6cb25 commit df941d9e7491c782210dfb2bbb11ee4bf1e6cb25 Author: Corentin Gay <gay@adacore.com> Date: Thu Dec 31 21:37:40 2020 -0300 Split wchars tests from the normal variant This change extracts apart the wchar specific parts of character conversion tests to allow conditonalizating these parts on actual wchar support while applying the rest more generally. This turned out useful during our work on the libstdc++ support for VxWorks, to expose the problematic areas more precisely. for libstdc++-v3/ChangeLog * testsuite/20_util/from_chars/1_neg.cc: Split wchar specific part into... * testsuite/20_util/from_chars/1_neg_wchar.cc: ... new file. Diff: --- libstdc++-v3/testsuite/20_util/from_chars/1_neg.cc | 8 ----- .../testsuite/20_util/from_chars/1_neg_wchar.cc | 35 ++++++++++++++++++++++ 2 files changed, 35 insertions(+), 8 deletions(-) diff --git a/libstdc++-v3/testsuite/20_util/from_chars/1_neg.cc b/libstdc++-v3/testsuite/20_util/from_chars/1_neg.cc index 0d2fe2b3e65..a84b0f5efb0 100644 --- a/libstdc++-v3/testsuite/20_util/from_chars/1_neg.cc +++ b/libstdc++-v3/testsuite/20_util/from_chars/1_neg.cc @@ -23,14 +23,6 @@ void test01(const char* first, const char* last) { -#if _GLIBCXX_USE_WCHAR_T - wchar_t wc; -#else - enum W { } wc; -#endif - std::from_chars(first, last, wc); // { dg-error "no matching" } - std::from_chars(first, last, wc, 10); // { dg-error "no matching" } - char16_t c16; std::from_chars(first, last, c16); // { dg-error "no matching" } std::from_chars(first, last, c16, 10); // { dg-error "no matching" } diff --git a/libstdc++-v3/testsuite/20_util/from_chars/1_neg_wchar.cc b/libstdc++-v3/testsuite/20_util/from_chars/1_neg_wchar.cc new file mode 100644 index 00000000000..2d736a28a2d --- /dev/null +++ b/libstdc++-v3/testsuite/20_util/from_chars/1_neg_wchar.cc @@ -0,0 +1,35 @@ +// Copyright (C) 2017-2018 Free Software Foundation, Inc. +// +// This file is part of the GNU ISO C++ Library. This library is free +// software; you can redistribute it and/or modify it under the +// terms of the GNU General Public License as published by the +// Free Software Foundation; either version 3, or (at your option) +// any later version. + +// This library is distributed in the hope that it will be useful, +// but WITHOUT ANY WARRANTY; without even the implied warranty of +// MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the +// GNU General Public License for more details. + +// You should have received a copy of the GNU General Public License along +// with this library; see the file COPYING3. If not see +// <http://www.gnu.org/licenses/>. + +// { dg-options "-std=gnu++17" } +// { dg-do compile { target c++17 } } +// { dg-require-wchars {} } + +#include <charconv> + +void +test01(const char* first, const char* last) +{ +#if _GLIBCXX_USE_WCHAR_T + wchar_t wc; +#else + enum W { } wc; +#endif + + std::from_chars(first, last, wc); // { dg-error "no matching" } + std::from_chars(first, last, wc, 10); // { dg-error "no matching" } +}
next reply other threads:[~2021-01-01 1:29 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-01 1:29 Alexandre Oliva [this message] -- strict thread matches above, loose matches on Subject: below -- 2021-01-01 5:22 Alexandre Oliva 2020-12-25 1:45 Alexandre Oliva 2020-12-18 14:46 Alexandre Oliva
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=20210101012915.F05B43857815@sourceware.org \ --to=aoliva@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: linkBe 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).