From: David Edelsohn <dje.gcc@gmail.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: "libstdc++" <libstdc++@gcc.gnu.org>,
GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: More new AIX errors
Date: Fri, 27 Nov 2020 12:50:17 -0500 [thread overview]
Message-ID: <CAGWvny=82q9z4T1f4AY7humr0gowhamE-f2OvYpzSiZNuQ9o+w@mail.gmail.com> (raw)
In-Reply-To: <20201126230202.GP1312820@redhat.com>
On Thu, Nov 26, 2020 at 6:02 PM Jonathan Wakely <jwakely@redhat.com> wrote:
>
> On 26/11/20 22:33 +0000, Jonathan Wakely wrote:
> >On 26/11/20 15:33 -0500, David Edelsohn via Libstdc++ wrote:
> >>Hi, Jonathan
> >>
> >>Thanks for the recent fixes. I still see a few errors that have crept
> >>in on AIX. All the same:
> >>
> >>FAIL: 17_intro/headers/c++2020/all_no_rtti.cc (test for excess errors)
> >>FAIL: 17_intro/headers/c++2020/all_pedantic_errors.cc (test for excess errors)
> >>FAIL: 17_intro/headers/c++2020/operator_names.cc (test for excess errors)
> >>FAIL: 17_intro/headers/c++2020/stdc++.cc (test for excess errors)
> >>FAIL: 17_intro/headers/c++2020/stdc++_multiple_inclusion.cc (test for
> >>excess errors)
> >>
> >>/tmp/GCC/powerpc-ibm-aix7.2.3.0/libstdc++-v3/include/latch:64: error:
> >>'notify_all' is not a member of 'std::__atomic_impl'
> >>/tmp/GCC/powerpc-ibm-aix7.2.3.0/libstdc++-v3/include/latch:75: error:
> >>'__atomic_wait' is not a member of 'std'; did you mean
> >>'__atomic_val_t'?
> >>
> >>Can you take a look when you have a moment?
> >
> >I think that was caused by r11-5436 which added <latch> to the
> >precompiled header <bits/stdc++.h>, and <latch> incorrectly assumes
> >that the atomic waiting functions are always available. They're not
> >available for the gthr-single.h multilib on AIX.
> >
> >I'm testing the fix now.
>
> And here it is. Committed to trunk.
That fixed it!
Thanks, David
prev parent reply other threads:[~2020-11-27 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-26 20:33 David Edelsohn
2020-11-26 22:33 ` Jonathan Wakely
2020-11-26 23:02 ` Jonathan Wakely
2020-11-27 17:50 ` David Edelsohn [this message]
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='CAGWvny=82q9z4T1f4AY7humr0gowhamE-f2OvYpzSiZNuQ9o+w@mail.gmail.com' \
--to=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@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).