public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Christophe Lyon <christophe.lyon@linaro.org>
To: Tom Honermann <tom@honermann.net>
Cc: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 4/4]: C++ P1423R3 char8_t remediation: New tests
Date: Tue, 03 Dec 2019 08:11:00 -0000	[thread overview]
Message-ID: <CAKdteOaNK1=NwPXp_1tyBob94BoHCq8dK-Gi=6pYSfkSJrA6fw@mail.gmail.com> (raw)
In-Reply-To: <423ff8de-b0df-71ce-07a9-ee82ae083334@honermann.net>

On Mon, 16 Sep 2019 at 04:34, Tom Honermann <tom@honermann.net> wrote:
>
> A revised patch is attached that modifies the tests for deleted ostream
> inserters to require C++2a.  This is required by the revision of patch
> 2/4 that adds proper preprocessor conditionals to the definitions.
>
> Tom.
>
> On 9/15/19 3:40 PM, Tom Honermann wrote:
> > This patch adds new tests to validate new deleted overloads of wchar_t,
> > char8_t, char16_t, and char32_t for ordinary and wide formatted
> > character and string ostream inserters.
> >
> > Additionally, new tests are added to validate invocations of u8path with
> > sequences of char8_t for both the C++17 and filesystem TS implementations.
> >
> > libstdc++-v3/ChangeLog:
> >
> > 2019-09-15  Tom Honermann  <tom@honermann.net>
> >
> >       *
> > libstdc++-v3/testsuite/27_io/basic_ostream/inserters_character/char/deleted.cc:
> >
> >         New test to validate deleted overloads of character and string
> >         inserters for narrow ostreams.
> >       *
> > libstdc++-v3/testsuite/27_io/basic_ostream/inserters_character/wchar_t/deleted.cc:
> >
> >         New test to validate deleted overloads of character and string
> >         inserters for wide ostreams.
> >       *
> > libstdc++-v3/testsuite/27_io/filesystem/path/factory/u8path-char8_t.cc:
> >         New test to validate u8path invocations with sequences of
> >         char8_t.
> >       *
> > libstdc++-v3/testsuite/experimental/filesystem/path/factory/u8path-char8_t.cc
> >
> >         New test to validate u8path invocations with sequences of
> >         char8_t.
> >

Hi,

I've noticed that the new test
27_io/filesystem/path/factory/u8path-char8_t.cc
fails to compile on arm-none-eabi with default cpu/fpu, because:
/tools/arm-none-eabi/bin/ld:
/obj-arm-none-eabi/gcc3/arm-none-eabi/libstdc++-v3/src/.libs/libstdc++.a(string-inst.o):
in function `_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEaSEOS4_':
string-inst.cc:(.text._ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEaSEOS4_[_ZNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEaSEOS4_]+0xf4):
undefined reference to `_ZSt15__alloc_on_moveISaIcEEvRT_S2_'
[etc...]

The one in experimental is unsupported thanks to
// { dg-require-filesystem-ts "" }
Should that be added to the version in 27_io?

Thanks,

Christophe

> > Tom.
>

  reply	other threads:[~2019-12-03  8:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-15 19:40 Tom Honermann
2019-09-16  2:34 ` Tom Honermann
2019-12-03  8:11   ` Christophe Lyon [this message]
2019-12-03  9:16     ` Jonathan Wakely
2019-12-05  8:01       ` Christophe Lyon
2019-12-05 11:43         ` Jonathan Wakely
2019-12-05 16:12           ` Christophe Lyon
2019-12-19  9:36             ` Jonathan Wakely
2019-12-20 17:11               ` Jonathan Wakely

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='CAKdteOaNK1=NwPXp_1tyBob94BoHCq8dK-Gi=6pYSfkSJrA6fw@mail.gmail.com' \
    --to=christophe.lyon@linaro.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=tom@honermann.net \
    /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).