public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/54847] --enable-libstdcxx-time=yes doesn't find the functional nanosleep() on darwin
Date: Mon, 08 Oct 2012 15:14:00 -0000	[thread overview]
Message-ID: <bug-54847-4-8Lf9dMu0Fc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54847-4@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54847

--- Comment #31 from Jack Howarth <howarth at nitro dot med.uc.edu> 2012-10-08 15:14:19 UTC ---
(In reply to comment #30)
> Can we take a step back and determine what exactly this PR is about?  Several
> of the comments make incorrect statements about the status quo, so I want to
> get the report clear.
> 
> I don't understand comment 1. 

The struct business is a red-herring and can be ignored. The test case without
struct
is compiled by g++ fine on darwin.

> 
> Contrary to comment 2, the configure check for sched_yield does *not* check
> _POSIX_TIMERS, so sched_yield should be used on darwin when
> --enable-libstdcxx-time is used.  Is _GLIBCXX_USE_SCHED_YIELD defined on darwin
> when the --enable-libstdcxx-time option is used?

I read libstdc++-v3/acinclude.m4 to imply that the check for sched_yield is
only used
when configure is passed --enable-libstdcxx-time=rt, I didn't bother with that
case on
darwin because Jeremy said....

  CLOCK_REALTIME isn't supported in darwin, so I wouldn't expect it to work
unless you had external implementation for the RT POSIX extension.

...off-list.

> 
> That option *doesn't* enable the use of clock_gettime on darwin, because the
> function isn't available. That's unavoidable.
> 
> That option does enable checking for nanosleep, but the check fails on darwin
> because nanosleep is available but darwin doesn't identify itself as supporting
> the Timers option (presumably because the rest of the option isn't supported.)
> 
> If that's correct, could we change the bug description to be more accurate?

Done. Note that the man page for darwin nanosleep() can be found at...

https://developer.apple.com/library/mac/#documentation/Darwin/Reference/ManPages/man2/nanosleep.2.html

and claims...

The nanosleep() function conforms to IEEE Std 1003.1b-1993 (``POSIX.1'').


  parent reply	other threads:[~2012-10-08 15:14 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-07 16:11 [Bug libstdc++/54847] New: --enable-libstdcxx-time=yes non-functional " howarth at nitro dot med.uc.edu
2012-10-07 17:31 ` [Bug libstdc++/54847] " paolo.carlini at oracle dot com
2012-10-07 17:40 ` jeremyhu at macports dot org
2012-10-07 18:02 ` paolo.carlini at oracle dot com
2012-10-07 18:35 ` jeremyhu at macports dot org
2012-10-07 18:51 ` howarth at nitro dot med.uc.edu
2012-10-07 18:54 ` howarth at nitro dot med.uc.edu
2012-10-07 19:04 ` jeremyhu at macports dot org
2012-10-07 19:22 ` howarth at nitro dot med.uc.edu
2012-10-07 19:38 ` jeremyhu at macports dot org
2012-10-07 19:43 ` howarth at nitro dot med.uc.edu
2012-10-07 20:11 ` howarth at nitro dot med.uc.edu
2012-10-07 22:17 ` howarth at nitro dot med.uc.edu
2012-10-07 22:29 ` howarth at nitro dot med.uc.edu
2012-10-07 22:51 ` jeremyhu at macports dot org
2012-10-07 23:03 ` paolo.carlini at oracle dot com
2012-10-07 23:07 ` jeremyhu at macports dot org
2012-10-07 23:14 ` roblu2184 at gmail dot com
2012-10-07 23:15 ` paolo.carlini at oracle dot com
2012-10-07 23:19 ` roblu2184 at gmail dot com
2012-10-07 23:26 ` jeremyhu at macports dot org
2012-10-07 23:33 ` paolo.carlini at oracle dot com
2012-10-08  3:48 ` jeremyhu at macports dot org
2012-10-08  9:26 ` paolo.carlini at oracle dot com
2012-10-08 10:06 ` redi at gcc dot gnu.org
2012-10-08 11:00 ` redi at gcc dot gnu.org
2012-10-08 11:17 ` redi at gcc dot gnu.org
2012-10-08 13:47 ` howarth at nitro dot med.uc.edu
2012-10-08 14:03 ` howarth at nitro dot med.uc.edu
2012-10-08 14:33 ` redi at gcc dot gnu.org
2012-10-08 14:47 ` redi at gcc dot gnu.org
2012-10-08 15:14 ` howarth at nitro dot med.uc.edu [this message]
2012-10-08 15:31 ` [Bug libstdc++/54847] --enable-libstdcxx-time=yes doesn't find the functional nanosleep() " howarth at nitro dot med.uc.edu
2012-10-08 15:55 ` redi at gcc dot gnu.org
2012-10-08 16:03 ` redi at gcc dot gnu.org
2012-10-08 16:31 ` howarth at nitro dot med.uc.edu
2012-10-08 16:45 ` howarth at nitro dot med.uc.edu
2012-10-08 16:48 ` [Bug libstdc++/54847] --enable-libstdcxx-time=yes doesn't find the function " redi at gcc dot gnu.org
2012-10-08 17:04 ` howarth at nitro dot med.uc.edu
2012-10-08 17:16 ` redi at gcc dot gnu.org
2012-10-08 18:33 ` jeremyhu at macports dot org
2012-10-08 19:50 ` redi at gcc dot gnu.org
2012-10-08 20:10 ` jeremyhu at macports dot org
2012-10-08 20:31 ` howarth at nitro dot med.uc.edu
2012-10-08 20:42 ` redi at gcc dot gnu.org
2012-10-08 22:27 ` howarth at nitro dot med.uc.edu
2012-10-09  0:46 ` howarth at nitro dot med.uc.edu
2012-10-10 23:20 ` redi at gcc dot gnu.org
2012-11-06 11:35 ` redi at gcc dot gnu.org

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=bug-54847-4-8Lf9dMu0Fc@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).