From: Jonathan Wakely <jwakely@redhat.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: Iain Sandoe <idsandoe@googlemail.com>,
libstdc++ <libstdc++@gcc.gnu.org>,
GCC Patches <gcc-patches@gcc.gnu.org>,
David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH] libstdc++: Add C++2a synchronization support
Date: Mon, 23 Nov 2020 18:31:20 +0000 [thread overview]
Message-ID: <20201123183120.GX1312820@redhat.com> (raw)
In-Reply-To: <CAH6eHdTvuG6x31LtB3-+fYqD2+f18rZca9-_FrgxDDj7q30Z4g@mail.gmail.com>
On 22/11/20 13:37 +0000, Jonathan Wakely via Libstdc++ wrote:
>On Sun, 22 Nov 2020, 12:29 Iain Sandoe, <idsandoe@googlemail.com> wrote:
>
>> thanks for looking at this over the weekend.
>>
>> Jonathan Wakely via Gcc-patches <gcc-patches@gcc.gnu.org> wrote:
>>
>> > On Sat, 21 Nov 2020 at 23:55, David Edelsohn via Libstdc++
>> > <libstdc++@gcc.gnu.org> wrote:
>> >> I am seeing 93 new libstdc++ failures on AIX, even after Jonathan's
>> >> fixes. And a few c++ failures with similar symptoms. I'm not certain
>> >> that it is due to this patch, but it's the likely suspect.
>> > Yes, it's that patch.
>> >
>> > This should fix most of those errors, but I haven't finished testing
>> > it, and can't commit it now anyway.
>> > <patch.txt>
>>
>> with r11-5235 + this patch there are still quite a few fails on Darwin -
>> but
>> all seem to be the same ( so maybe only problem ;) ):
>> “sem_timedwait was not declared in this scope”.
>>
>> It looks like the semaphore header is optional in SUSv3 (AFAIK that’s still
>> the claimed edition for Darwin) - and although Darwin has the semaphore
>> header, it doesn’t seem to have an impl. of sem_timedwait.
>>
>> just:
>> int sem_trywait(sem_t *);
>> int sem_wait(sem_t *) ;
>>
>
>
>It probably depends on the _POSIX_TIMEOUTS option which MacOS doesn't
>support (optional in POSIX 2001, but not 2008).
Hopefully this fixes it, but I haven't tested it on darwin, only
linux, aix and solaris.
Committed.
next prev parent reply other threads:[~2020-11-23 18:31 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-21 23:54 David Edelsohn
2020-11-22 1:27 ` Jonathan Wakely
2020-11-22 12:29 ` Iain Sandoe
2020-11-22 13:37 ` Jonathan Wakely
2020-11-23 18:31 ` Jonathan Wakely [this message]
2020-11-23 18:31 ` Jonathan Wakely
2020-11-24 1:48 ` David Edelsohn
2020-11-23 18:30 ` Jonathan Wakely
-- strict thread matches above, loose matches on Subject: below --
2020-10-23 10:28 [PATCH] t/trodgers/c2a_synchronization Jonathan Wakely
2020-10-26 21:48 ` [PATCH] libstdc++: Add C++2a synchronization support Thomas Rodgers
2020-10-27 10:23 ` Jonathan Wakely
2020-11-20 22:44 ` Thomas Rodgers
2020-11-22 21:13 ` Stephan Bergmann
2020-11-23 18:33 ` Jonathan Wakely
2020-11-22 21:41 ` Stephan Bergmann
2020-11-23 18:32 ` Jonathan Wakely
2020-11-21 15:16 ` Andreas Schwab
2020-11-21 17:04 ` Jonathan Wakely
2020-11-21 17:39 ` Jonathan Wakely
2020-11-22 0:36 ` H.J. Lu
2020-11-23 14:50 ` Jonathan Wakely
2020-11-24 23:45 ` Jonathan Wakely
2020-11-25 1:07 ` Jonathan Wakely
2020-11-25 10:35 ` Jonathan Wakely
2020-11-25 12:32 ` Jonathan Wakely
2020-11-25 18:39 ` Jonathan Wakely
2020-11-26 16:26 ` Jonathan Wakely
2020-11-23 16:08 ` Jonathan Wakely
2020-09-03 0:54 [PATCH] " Thomas Rodgers
2020-09-11 23:58 ` [PATCH] libstdc++: " Thomas Rodgers
2020-09-28 13:25 ` Jonathan Wakely
2020-10-01 23:37 ` Thomas Rodgers
2020-10-02 15:40 ` Thomas Rodgers
2020-09-28 13:30 ` Jonathan Wakely
2020-09-28 13:36 ` Jonathan Wakely
2020-09-28 21:29 ` Thomas Rodgers
2020-09-29 9:44 ` 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=20201123183120.GX1312820@redhat.com \
--to=jwakely@redhat.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=idsandoe@googlemail.com \
--cc=jwakely.gcc@gmail.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).