public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: "CHIGOT, CLEMENT" <clement.chigot@atos.net>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: libstdc++ <libstdc++@gcc.gnu.org>,
	Jonathan Wakely <jwakely@redhat.com>,
	David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH] libstdc++: implement locale support for AIX
Date: Thu, 22 Jul 2021 12:09:06 +0000	[thread overview]
Message-ID: <PA4PR02MB6686BFAA4B2E4319FEFAF4D7EAE49@PA4PR02MB6686.eurprd02.prod.outlook.com> (raw)
In-Reply-To: <yddr1frlsw8.fsf@CeBiTec.Uni-Bielefeld.DE>

Hi Rainer,

>> A part from that it would be good if someone familiar with
>> freebsd or dragonfly can take a look at it. There shouldn't be
>> any problems but it needs to be tested and a few #ifdef remain
>> for these two targets.
>
> I'd tried DragonflyBSD quite some time ago, but couldn't even get it to
> boot in VirtualBox and didn't want to spend too much time on it.
>
> However, the last i586-unknown-freebsd11.4 test results for unmodified
> trunk are still terrible, showing 101 FAILs in libstdc++, a large number
> among those being locale tests.  I had seen (not unexpectedly) similarly
> abysmal results when I tried an earlier version of your patch on (I
> believe) FreeBSD 12 in VirtualBox some time ago, which made me question
> if that clocale implementation is a good basis for xpg7 if it doesn't
> even work on the target it's supposed to support.
>
> Could you please share the libstdc++-v3 mail-report.log snippet you get
> on AIX with your latest patch as a point of comparison?

Here are the result for AIX 32bit. Those are a bit different in 64bit but not much.
However, I don't have all the locale installed so some are skipped.

Native configuration is powerpc-ibm-aix7.2.3.0

                === libstdc++ tests ===


Running target unix
FAIL: 17_intro/headers/c++1998/charset.cc (test for excess errors)
FAIL: 17_intro/headers/c++2011/charset.cc (test for excess errors)
FAIL: 17_intro/headers/c++2014/charset.cc (test for excess errors)
FAIL: 17_intro/headers/c++2017/charset.cc (test for excess errors)
FAIL: 17_intro/headers/c++2020/charset.cc (test for excess errors)
UNRESOLVED: 22_locale/codecvt/in/wchar_t/4.cc compilation failed to produce executable
UNRESOLVED: 22_locale/codecvt/in/wchar_t/8.cc compilation failed to produce executable
UNRESOLVED: 22_locale/codecvt/in/wchar_t/9.cc compilation failed to produce executable
UNRESOLVED: 22_locale/codecvt/length/wchar_t/4.cc compilation failed to produce executable
FAIL: 22_locale/codecvt/max_length/wchar_t/4.cc execution test
UNRESOLVED: 22_locale/codecvt/out/wchar_t/4.cc compilation failed to produce executable
UNRESOLVED: 22_locale/codecvt/unshift/wchar_t/4.cc compilation failed to produce executable
FAIL: 22_locale/ctype/is/char/wrapped_env.cc execution test
FAIL: 22_locale/time_get/get_date/char/12750.cc execution test
FAIL: 22_locale/time_get/get_date/wchar_t/12750.cc execution test
FAIL: 22_locale/time_put/put/char/2.cc execution test
FAIL: 22_locale/time_put/put/wchar_t/2.cc execution test
FAIL: 23_containers/unordered_map/96088.cc execution test
FAIL: 23_containers/unordered_multimap/96088.cc execution test
FAIL: 23_containers/unordered_multiset/96088.cc execution test
FAIL: 23_containers/unordered_set/96088.cc execution test
FAIL: 27_io/filesystem/iterators/directory_iterator.cc execution test
FAIL: 27_io/filesystem/iterators/recursive_directory_iterator.cc execution test
FAIL: 27_io/filesystem/operations/canonical.cc execution test
FAIL: 27_io/filesystem/operations/exists.cc execution test
FAIL: 27_io/filesystem/operations/is_empty.cc execution test
FAIL: 27_io/filesystem/operations/remove.cc execution test
FAIL: 27_io/filesystem/operations/remove_all.cc execution test
FAIL: 27_io/filesystem/operations/status.cc execution test
FAIL: 27_io/filesystem/operations/symlink_status.cc execution test
FAIL: 27_io/filesystem/operations/temp_directory_path.cc execution test
FAIL: 27_io/filesystem/operations/weakly_canonical.cc execution test
FAIL: 27_io/manipulators/extended/get_time/char/2.cc execution test
FAIL: decimal/binary-arith.cc (test for excess errors)
UNRESOLVED: decimal/binary-arith.cc compilation failed to produce executable
FAIL: decimal/comparison.cc (test for excess errors)
UNRESOLVED: decimal/comparison.cc compilation failed to produce executable
FAIL: decimal/compound-assignment-memfunc.cc (test for excess errors)
UNRESOLVED: decimal/compound-assignment-memfunc.cc compilation failed to produce executable
FAIL: decimal/compound-assignment.cc (test for excess errors)
UNRESOLVED: decimal/compound-assignment.cc compilation failed to produce executable
FAIL: decimal/make-decimal.cc (test for excess errors)
UNRESOLVED: decimal/make-decimal.cc compilation failed to produce executable
FAIL: decimal/pr54036-1.cc (test for excess errors)
UNRESOLVED: decimal/pr54036-1.cc compilation failed to produce executable
FAIL: decimal/pr54036-2.cc (test for excess errors)
UNRESOLVED: decimal/pr54036-2.cc compilation failed to produce executable
FAIL: decimal/pr54036-3.cc (test for excess errors)
UNRESOLVED: decimal/pr54036-3.cc compilation failed to produce executable
FAIL: decimal/unary-arith.cc (test for excess errors)
UNRESOLVED: decimal/unary-arith.cc compilation failed to produce executable
FAIL: experimental/filesystem/iterators/directory_iterator.cc execution test
FAIL: experimental/filesystem/iterators/recursive_directory_iterator.cc execution test
FAIL: experimental/filesystem/operations/exists.cc execution test
FAIL: experimental/filesystem/operations/is_empty.cc execution test
FAIL: experimental/filesystem/operations/remove.cc execution test
FAIL: experimental/filesystem/operations/remove_all.cc execution test
FAIL: experimental/filesystem/operations/temp_directory_path.cc execution test
FAIL: ext/codecvt/wchar_t.cc execution test

                === libstdc++ Summary ===

# of expected passes            13692
# of unexpected failures        44
# of expected failures          114
# of unresolved testcases       15
# of unsupported tests          559


If you can, can you show me the result for FreeBSD, I might have already
encountered some of the failures while developing AIX version.

Thanks,
Clément




  reply	other threads:[~2021-07-22 12:09 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <PA4PR02MB6686075C6C254E583B72BC2AEAAB0@PA4PR02MB6686.eurprd02.prod.outlook.com>
     [not found] ` <CAGWvny=XpcWGnyb=MWg5ziYSND7O1AnQ6-NAX811p1b5urH0YA@mail.gmail.com>
2021-01-11 15:35   ` Rainer Orth
2021-01-11 15:40     ` Jonathan Wakely
2021-01-11 15:56       ` CHIGOT, CLEMENT
2021-01-11 22:20         ` David Edelsohn
2021-01-12 15:14           ` CHIGOT, CLEMENT
2021-01-12 15:23             ` CHIGOT, CLEMENT
2021-01-12 15:25             ` Jonathan Wakely
2021-01-12 15:40               ` CHIGOT, CLEMENT
2021-01-12 15:44               ` David Edelsohn
2021-01-12 17:34                 ` Jonathan Wakely
2021-01-12 15:52               ` Rainer Orth
2021-01-12 17:41                 ` Rainer Orth
2021-01-12 17:44                   ` David Edelsohn
2021-01-12 19:58                     ` Rainer Orth
2021-01-13 11:57                       ` Rainer Orth
2021-01-13 12:23                         ` CHIGOT, CLEMENT
2021-01-13 12:31                           ` Rainer Orth
2021-01-13 12:41                             ` CHIGOT, CLEMENT
2021-01-13 12:47                               ` Rainer Orth
2021-01-21 12:48                                 ` CHIGOT, CLEMENT
2021-01-21 16:36                                   ` Rainer Orth
2021-01-22  9:57                                     ` CHIGOT, CLEMENT
2021-01-22 11:04                                       ` Rainer Orth
2021-01-22 11:29                                         ` Jonathan Wakely
2021-01-22 11:54                                           ` Rainer Orth
2021-01-22 12:23                                             ` CHIGOT, CLEMENT
2021-01-27 12:52                                               ` CHIGOT, CLEMENT
2021-01-27 14:26                                                 ` Rainer Orth
2021-01-27 14:44                                                   ` CHIGOT, CLEMENT
2021-01-28 10:09                                                     ` CHIGOT, CLEMENT
2021-05-17  9:17                                                       ` CHIGOT, CLEMENT
2021-06-08  6:59                                                         ` CHIGOT, CLEMENT
2021-06-09 14:50                                                           ` Rainer Orth
2021-07-21 12:00                                                             ` CHIGOT, CLEMENT
2021-07-21 13:04                                                               ` Rainer Orth
2021-07-22 12:09                                                                 ` CHIGOT, CLEMENT [this message]
2021-07-22 12:19                                                                   ` Rainer Orth
2021-07-30 14:02                                                                     ` CHIGOT, CLEMENT
2022-03-16  9:57                                                                       ` CHIGOT, CLEMENT
2021-01-22 11:12                                       ` Jonathan Wakely
2021-01-22 11:02                                     ` Jonathan Wakely
2021-01-12 16:00             ` Rainer Orth
     [not found]   ` <PA4PR02MB6686C2022E2B42D82DC9F269EAAB0@PA4PR02MB6686.eurprd02.prod.outlook.com>
2021-01-11 15:38     ` Rainer Orth

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=PA4PR02MB6686BFAA4B2E4319FEFAF4D7EAE49@PA4PR02MB6686.eurprd02.prod.outlook.com \
    --to=clement.chigot@atos.net \
    --cc=dje.gcc@gmail.com \
    --cc=jwakely@redhat.com \
    --cc=libstdc++@gcc.gnu.org \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    /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).