[Bug target/54407] New: FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[Bug target/54407] New: FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[dominiq at lps dot ens.fr]

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

             Bug #: 54407
           Summary: FAIL: 30_threads/condition_variable/54185.cc execution
                    test  program timed out on powerpc-apple-darwin9 and
                    x86_64-apple-darwin10
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: target
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: dominiq@lps.ens.fr
                CC: howarth@bromo.med.uc.edu, iains@gcc.gnu.org,
                    redi@gcc.gnu.org
              Host: powerpc-apple-darwin9 x86_64-apple-darwin10
            Target: powerpc-apple-darwin9 x86_64-apple-darwin10
             Build: powerpc-apple-darwin9 x86_64-apple-darwin10


On powerpc-apple-darwin9 and x86_64-apple-darwin10, the test
30_threads/condition_variable/54185.cc is timed out (from
http://gcc.gnu.org/ml/gcc-testresults/2012-08/msg02572.html this does seem to
occur on x86_64-apple-darwin12.2.0). Sampling the run after ~40 minutes gives:

Sampling process 47649 for 3 seconds with 1 millisecond of run time between
samples
Sampling completed, processing symbols...
Analysis of sampling a.out (pid 47649) every 1 millisecond
Process:         a.out [47649]
Path:            /Users/dominiq/Documents/Fortran/g95bench/win/f90/bug/a.out
Load Address:    0x100000000
Identifier:      a.out
Version:         ??? (???)
Code Type:       X86-64 (Native)
Parent Process:  tcsh [418]

Date/Time:       2012-08-26 22:04:25.062 +0200
OS Version:      Mac OS X 10.6.8 (10K549)
Report Version:  6

Call graph:
    2130 Thread_27669825   DispatchQueue_1: com.apple.main-thread  (serial)
      2130 start
        2130 main
          2130 std::thread::join()
            2130 pthread_join
              2130 __semwait_signal
    2130 Thread_27669827
      2130 thread_start
        2130 std::condition_variable::wait(std::unique_lock<std::mutex>&)
          2130 __spin_lock
    2130 Thread_27669828
      2130 thread_start
        2130 std::condition_variable::wait(std::unique_lock<std::mutex>&)
          2130 __spin_lock
    2130 Thread_27669829
      2130 thread_start
        2130 std::condition_variable::wait(std::unique_lock<std::mutex>&)
          2130 __spin_lock
    2130 Thread_27669830
      2130 thread_start
        2130 std::condition_variable::wait(std::unique_lock<std::mutex>&)
          2130 __spin_lock
    2130 Thread_27669831
      2130 thread_start
        2130 std::condition_variable::wait(std::unique_lock<std::mutex>&)
          2130 __spin_lock
    2130 Thread_27669832
      2130 thread_start
        2130 std::condition_variable::wait(std::unique_lock<std::mutex>&)
          2130 __spin_lock
    2130 Thread_27669833
      2130 thread_start
        2130 std::condition_variable::wait(std::unique_lock<std::mutex>&)
          2130 __spin_lock
    2130 Thread_27669834
      2130 thread_start
        2130 std::condition_variable::wait(std::unique_lock<std::mutex>&)
          2130 __spin_lock

Total number in stack (recursive counted multiple, when >=5):
        8       __spin_lock
        8       std::condition_variable::wait(std::unique_lock<std::mutex>&)
        8       thread_start

Sort by top of stack, same collapsed (when >= 5):
        __spin_lock        17040
        __semwait_signal        2130

Binary Images:
       0x100000000 -        0x100001ff7 +a.out ??? (???)
<1BA5F363-960B-6D52-5641-2CE7E1635197>
/Users/dominiq/Documents/Fortran/g95bench/win/f90/bug/a.out
       0x100007000 -        0x1000abfe7 +libstdc++.6.dylib 7.17.0
(compatibility 7.0.0) <58262B92-ECCD-BD30-9402-ED87BC90A8EB>
/opt/gcc/gcc4.8w/lib/libstdc++.6.dylib
       0x100138000 -        0x10014cfef +libgcc_s.1.dylib ??? (???)
<91DF981B-4585-E9BF-8747-487D8A834B9D> /opt/gcc/gcc4.8w/lib/libgcc_s.1.dylib
    0x7fff5fc00000 -     0x7fff5fc3bdef  dyld 132.1 (???)
<B536F2F1-9DF1-3B6C-1C2C-9075EA219A06> /usr/lib/dyld
    0x7fff80d89000 -     0x7fff80f4afef  libSystem.B.dylib 125.2.11
(compatibility 1.0.0) <9AB4F1D1-89DC-0E8A-DC8E-A4FE4D69DB69>
/usr/lib/libSystem.B.dylib
    0x7fff892a9000 -     0x7fff893a1ff7  libiconv.2.dylib 7.0.0 (compatibility
7.0.0) <7E4ADB5A-CC77-DCFD-3E54-2F35A2C8D95A> /usr/lib/libiconv.2.dylib
    0x7fff89728000 -     0x7fff8972cff7  libmathCommon.A.dylib 315.0.0
(compatibility 1.0.0) <95718673-FEEE-B6ED-B127-BCDBDB60D4E5>
/usr/lib/system/libmathCommon.A.dylib
    0x7fffffe00000 -     0x7fffffe01fff  libSystem.B.dylib ??? (???)
<9AB4F1D1-89DC-0E8A-DC8E-A4FE4D69DB69> /usr/lib/libSystem.B.dylib
Sample analysis of process 47649 written to file /dev/stdout

[Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[redi at gcc dot gnu.org]

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

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-08-30 10:42:07 UTC ---
(In reply to comment #0)
> On powerpc-apple-darwin9 and x86_64-apple-darwin10, the test
> 30_threads/condition_variable/54185.cc is timed out (from
> http://gcc.gnu.org/ml/gcc-testresults/2012-08/msg02572.html this does seem to
> occur on x86_64-apple-darwin12.2.0).

Do you mean does *not* happen on darwin12?

> Sampling the run after ~40 minutes gives:

There's no need to wait 40 mins, the process will be deadlocked after a few
milliseconds.

I can't look into this for a week, but it looks like notify_all only woke one
of the nine threads waiting on the condition variable, which would be a darwin
bug. That looks more likely if it doesn't happen on later versions.

[Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[dominiq at lps dot ens.fr]

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

--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2012-08-30 12:53:54 UTC ---
(In reply to comment #1)
> Do you mean does *not* happen on darwin12?

Well, I don't have access to darwin11 nor 12, so the only thing I am sure of is
that the failure does not show up in the darwin12 logs.

> ... which would be a darwin bug.
> That looks more likely if it doesn't happen on later versions.

I agree, but I doubt that apple will backport the fix. Does it exist a simple
workaround? If not, the test should be skipped for darwin before 10 (maybe 11).

[Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[redi at gcc dot gnu.org]

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

--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-08-30 16:40:48 UTC ---
I don't know of any workaround so disabling the test seems like a good option

[Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[dominiq at lps dot ens.fr]

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

--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2012-10-14 17:08:09 UTC ---
> I don't know of any workaround so disabling the test seems like a good option

What about

--- libstdc++-v3/testsuite/30_threads/condition_variable/54185.cc    2012-08-17
14:14:36.000000000 +0200
+++ ../work/libstdc++-v3/testsuite/30_threads/condition_variable/54185.cc   
2012-10-14 18:52:22.000000000 +0200
@@ -1,4 +1,5 @@
-// { dg-do run { target *-*-freebsd* *-*-netbsd* *-*-linux* *-*-solaris*
*-*-cygwin *-*-darwin* powerpc-ibm-aix* } }
+// { dg-do run { target *-*-freebsd* *-*-netbsd* *-*-linux* *-*-solaris*
*-*-cygwin *-*-darwin1[1-9]* powerpc-ibm-aix* } }
+// { dg-do compile { target *-*-darwin[4-9]* *-*-darwin10* } }
 // { dg-options " -std=gnu++0x -pthread" { target *-*-freebsd* *-*-netbsd*
*-*-linux* powerpc-ibm-aix* } }
 // { dg-options " -std=gnu++0x -pthreads" { target *-*-solaris* } }
 // { dg-options " -std=gnu++0x " { target *-*-cygwin *-*-darwin* } }

? Jack could you verify that the test actually run on darwin(11|12) after the
patch? TIA.

[Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[howarth at nitro dot med.uc.edu]

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

Jack Howarth <howarth at nitro dot med.uc.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |howarth at nitro dot
                   |                            |med.uc.edu

--- Comment #5 from Jack Howarth <howarth at nitro dot med.uc.edu> 2012-10-14 18:35:19 UTC ---
The patch in comment 4 with...

make -k check
RUNTESTFLAGS="conformance.exp=30_threads/condition_variable/54185.cc
--target_board=unix'{-m32,-m64}'"

produces...

Native configuration is x86_64-apple-darwin11.4.2

        === libstdc++ tests ===

Schedule of variations:
    unix/-m32
    unix/-m64

Running target unix/-m32
Using /sw/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /sw/share/dejagnu/config/unix.exp as generic interface file for target.
Using
/sw/src/fink.build/gcc48-4.8.0-1000/gcc-4.8-20121007/libstdc++-v3/testsuite/config/default.exp
as tool-and-target-specific interface file.
Running
/sw/src/fink.build/gcc48-4.8.0-1000/gcc-4.8-20121007/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp
...

        === libstdc++ Summary for unix/-m32 ===

# of expected passes        1
Running target unix/-m64
Using /sw/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /sw/share/dejagnu/config/unix.exp as generic interface file for target.
Using
/sw/src/fink.build/gcc48-4.8.0-1000/gcc-4.8-20121007/libstdc++-v3/testsuite/config/default.exp
as tool-and-target-specific interface file.
Running
/sw/src/fink.build/gcc48-4.8.0-1000/gcc-4.8-20121007/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp
...

        === libstdc++ Summary for unix/-m64 ===

# of expected passes        1

        === libstdc++ Summary ===

# of expected passes        2

[Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[dominiq at lps dot ens.fr]

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

--- Comment #6 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2012-10-14 19:06:32 UTC ---
> The patch in comment 4 with...
>
> make -k check
> RUNTESTFLAGS="conformance.exp=30_threads/condition_variable/54185.cc
> --target_board=unix'{-m32,-m64}'"
>
> produces...

Could you check in the log file that the test is actually run?

[Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[howarth at nitro dot med.uc.edu]

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

--- Comment #7 from Jack Howarth <howarth at nitro dot med.uc.edu> 2012-10-14 20:14:01 UTC ---
(In reply to comment #6)
> > The patch in comment 4 with...
> >
> > make -k check
> > RUNTESTFLAGS="conformance.exp=30_threads/condition_variable/54185.cc
> > --target_board=unix'{-m32,-m64}'"
> >
> > produces...
> 
> Could you check in the log file that the test is actually run?

The dg-compile line oddly seems to suppress the running of the compiled test.
Dropping that line gives...


Native configuration is x86_64-apple-darwin11.4.2

        === libstdc++ tests ===

Schedule of variations:
    unix/-m32
    unix/-m64

Running target unix/-m32
Using /sw/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /sw/share/dejagnu/config/unix.exp as generic interface file for target.
Using
/sw/src/fink.build/gcc48-4.8.0-1000/gcc-4.8-20121007/libstdc++-v3/testsuite/config/default.exp
as tool-and-target-specific interface file.
Running
/sw/src/fink.build/gcc48-4.8.0-1000/gcc-4.8-20121007/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp
...

        === libstdc++ Summary for unix/-m32 ===

# of expected passes        2
Running target unix/-m64
Using /sw/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /sw/share/dejagnu/config/unix.exp as generic interface file for target.
Using
/sw/src/fink.build/gcc48-4.8.0-1000/gcc-4.8-20121007/libstdc++-v3/testsuite/config/default.exp
as tool-and-target-specific interface file.
Running
/sw/src/fink.build/gcc48-4.8.0-1000/gcc-4.8-20121007/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp
...

        === libstdc++ Summary for unix/-m64 ===

# of expected passes        2

        === libstdc++ Summary ===

# of expected passes        4

Why you want to bother to compile the test are darwins which can't safely run
it anyway. That seems rather pointless.

[Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[dominiq at lps dot ens.fr]

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

--- Comment #8 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2012-10-14 20:48:21 UTC ---
> The dg-compile line oddly seems to suppress the running of the compiled test. ...

What happens if you replace the line

// { dg-do compile { target *-*-darwin[4-9]* *-*-darwin10* } }

with

// { dg-do compile { target *-*-darwin9* *-*-darwin10* } }

?

[Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[howarth at nitro dot med.uc.edu]

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

--- Comment #9 from Jack Howarth <howarth at nitro dot med.uc.edu> 2012-10-14 20:53:56 UTC ---
(In reply to comment #8)
> > The dg-compile line oddly seems to suppress the running of the compiled test. ...
> 
> What happens if you replace the line
> 
> // { dg-do compile { target *-*-darwin[4-9]* *-*-darwin10* } }
> 
> with
> 
> // { dg-do compile { target *-*-darwin9* *-*-darwin10* } }
> 
> ?

Still suppresses the execution of the test on x86_64-apple-darwin12. Are there
any examples in the FSF gcc testsuites of dg-run being used at the same time as
dg-compile? I suspect that is an unsupported combination.

[Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[howarth at nitro dot med.uc.edu]

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

--- Comment #10 from Jack Howarth <howarth at nitro dot med.uc.edu> 2012-10-14 21:12:20 UTC ---
I think you need to use...

// { dg-xfail-if "broken pthreads before darwin10" { *-*-darwin9* *-*-darwin10*
} { "*" } { "" } }

instead of dg-do-compile. From
http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gccint/Test-Directives.html,
note...

If the directive includes the optional `{ xfail selector }' and the selector is
met then the test is expected to fail. For dg-do run, execution is expected to
fail but compilation is expected to pass. 

since you already are passing dg-do-run a target selector, an additional
dg-xfail-if is required. This
combination works here on x86_64-apple-darwin12....

Index: libstdc++-v3/testsuite/30_threads/condition_variable/54185.cc
===================================================================
--- libstdc++-v3/testsuite/30_threads/condition_variable/54185.cc    (revision
192440)
+++ libstdc++-v3/testsuite/30_threads/condition_variable/54185.cc    (working
copy)
@@ -1,4 +1,5 @@
-// { dg-do run { target *-*-freebsd* *-*-netbsd* *-*-linux* *-*-solaris*
*-*-cygwin *-*-darwin* powerpc-ibm-aix* } }
+// { dg-do run { target *-*-freebsd* *-*-netbsd* *-*-linux* *-*-solaris*
*-*-cygwin *-*-darwin1[1-9]* powerpc-ibm-aix* } }
+// { dg-xfail-if "broken pthreads before darwin10" { *-*-darwin9*
*-*-darwin10* } { "*" } { "" } }
 // { dg-options " -std=gnu++0x -pthread" { target *-*-freebsd* *-*-netbsd*
*-*-linux* powerpc-ibm-aix* } }
 // { dg-options " -std=gnu++0x -pthreads" { target *-*-solaris* } }
 // { dg-options " -std=gnu++0x " { target *-*-cygwin *-*-darwin* } }

[Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[howarth at nitro dot med.uc.edu]

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

--- Comment #11 from Jack Howarth <howarth at nitro dot med.uc.edu> 2012-10-14 21:13:18 UTC ---
The comment should be corrected to "broken pthreads before darwin11".

[Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[dominiq at lps dot ens.fr]

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

--- Comment #12 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2012-10-14 21:17:47 UTC ---
> Still suppresses the execution of the test on x86_64-apple-darwin12. Are there
> any examples in the FSF gcc testsuites of dg-run being used at the same time as
> dg-compile? 

Yes (I did not invent it, I tried it because I saw it):
gcc.dg/vect/vect-(82|83)_64.c for instance.

/* { dg-do run { target { { powerpc*-*-* && lp64 } && powerpc_altivec_ok } } }
*/
/* { dg-do compile { target { { powerpc*-*-* && ilp32 } && powerpc_altivec_ok }
} } */
/* { dg-options "-O2 -ftree-vectorize -mpowerpc64 -fdump-tree-vect-stats
-maltivec" } */

> I suspect that is an unsupported combination.

Now you asked the question, the test is not run on powerpc-apple-darwin9 with
-m64.
Could you try to put the 'dg-do compile' line before the 'dg-do run' one?

[Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[howarth at nitro dot med.uc.edu]

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

--- Comment #13 from Jack Howarth <howarth at nitro dot med.uc.edu> 2012-10-14 21:22:48 UTC ---
I would rather we use...

Index: libstdc++-v3/testsuite/30_threads/condition_variable/54185.cc
===================================================================
--- libstdc++-v3/testsuite/30_threads/condition_variable/54185.cc    (revision
192440)
+++ libstdc++-v3/testsuite/30_threads/condition_variable/54185.cc    (working
copy)
@@ -1,4 +1,5 @@
-// { dg-do run { target *-*-freebsd* *-*-netbsd* *-*-linux* *-*-solaris*
*-*-cygwin *-*-darwin* powerpc-ibm-aix* } }
+// { dg-do run { target *-*-freebsd* *-*-netbsd* *-*-linux* *-*-solaris*
*-*-cygwin *-*-darwin1[1-9]* powerpc-ibm-aix* } }
+// { dg-xfail-if "broken pthreads before darwin11" { *-*-darwin9*
*-*-darwin10* } { "*" } { "" } }
 // { dg-options " -std=gnu++0x -pthread" { target *-*-freebsd* *-*-netbsd*
*-*-linux* powerpc-ibm-aix* } }
 // { dg-options " -std=gnu++0x -pthreads" { target *-*-solaris* } }
 // { dg-options " -std=gnu++0x " { target *-*-cygwin *-*-darwin* } }

The usage of dg-skip-if allows the test to be both compiled and executed on
darwin1 in concert with dg-do-run. If it is working as documented, the
dg-skip-if above to only compile on darwin9/10 but not try to execute the test
case.

[Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[dominiq at lps dot ens.fr]

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

--- Comment #14 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2012-10-14 21:34:55 UTC ---
> > I suspect that is an unsupported combination.
>
> Now you asked the question, the test is not run on powerpc-apple-darwin9 
> with -m64.
> Could you try to put the 'dg-do compile' line before the 'dg-do run' one?

This does not work either, it seems that the last dg-do is used.

Note that the test is not compiled with dg-skip-if. With dg-xfail-if as in
comment #10,  test is not compiled, but as in comment #13, I get a XPASS and
the test is run.

[Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[howarth at nitro dot med.uc.edu]

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

--- Comment #15 from Jack Howarth <howarth at nitro dot med.uc.edu> 2012-10-14 22:17:07 UTC ---
I still don't see the point of testing the compilation of a test which doesn't
execute properly. I also suspect resorting to a non-standard approach in
deja-gnu will never make it pass the review process.

[Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[redi at gcc dot gnu.org]

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

--- Comment #16 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-10-16 10:07:31 UTC ---
Agreed, please just disable the test entirely on the targets where it fails

[Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[dominiq at lps dot ens.fr]

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

--- Comment #17 from Dominique d'Humieres <dominiq at lps dot ens.fr> 2013-03-10 17:58:17 UTC ---
Jack,

I see at http://gcc.gnu.org/ml/gcc-testresults/2012-11/msg00331.html that you
have tested a fix for this PR. I have tested that it skips the test on
powerpc-apple-darwin9 and x86_64-apple-darwin10. Have you submitted it?

[Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[howarth at nitro dot med.uc.edu]

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

--- Comment #18 from Jack Howarth <howarth at nitro dot med.uc.edu> 2013-03-11 14:51:01 UTC ---
(In reply to comment #17)
> Jack,
> 
> I see at http://gcc.gnu.org/ml/gcc-testresults/2012-11/msg00331.html that you
> have tested a fix for this PR. I have tested that it skips the test on
> powerpc-apple-darwin9 and x86_64-apple-darwin10. Have you submitted it?

I posted this patch back in Oct as...

http://gcc.gnu.org/ml/libstdc++/2012-10/msg00111.html

Mike wanted a comment about an associated radar which doesn't exist. As far as
I know this bug was fixed in the pthread rewrites for darwin11 and later.

[Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[dominiq at lps dot ens.fr]

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

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2013-06-29
     Ever confirmed|0                           |1

--- Comment #19 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> I posted this patch back in Oct as...
>
> http://gcc.gnu.org/ml/libstdc++/2012-10/msg00111.html
>
> Mike wanted a comment about an associated radar which doesn't exist. 
> As far as I know this bug was fixed in the pthread rewrites for darwin11 
> and later.

Could someone commit the patch?

[Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[paolo.carlini at oracle dot com]

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

--- Comment #20 from Paolo Carlini <paolo.carlini at oracle dot com> ---
Commit *what*? Please add a link to something actually OKed.

[Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[dominiq at gcc dot gnu.org]

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

--- Comment #21 from dominiq at gcc dot gnu.org ---
Author: dominiq
Date: Wed Apr  2 08:44:40 2014
New Revision: 209017

URL: http://gcc.gnu.org/viewcvs?rev=209017&root=gcc&view=rev
Log:
2014-04-02  Dominique d'Humieres  <dominiq@lps.ens.fr>
        Jack Howarth <howarth@bromo.med.uc.edu>

    PR target/54407
    * testsuite/30_threads/condition_variable/54185.cc: Skip for
    darwin < 11.


Modified:
    trunk/libstdc++-v3/ChangeLog
    trunk/libstdc++-v3/testsuite/30_threads/condition_variable/54185.cc

[Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[dominiq at gcc dot gnu.org]

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

--- Comment #22 from dominiq at gcc dot gnu.org ---
Author: dominiq
Date: Sat Apr  5 12:25:37 2014
New Revision: 209152

URL: http://gcc.gnu.org/viewcvs?rev=209152&root=gcc&view=rev
Log:
2012-04-06  Dominique d'Humieres  <dominiq@lps.ens.fr>
        Jack Howarth <howarth@bromo.med.uc.edu>

    PR target/54407
    * 30_threads/condition_variable/54185.cc: Skip for darwin < 11.


Modified:
    branches/gcc-4_8-branch/libstdc++-v3/ChangeLog
   
branches/gcc-4_8-branch/libstdc++-v3/testsuite/30_threads/condition_variable/54185.cc

[Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[dominiq at gcc dot gnu.org]

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

--- Comment #23 from dominiq at gcc dot gnu.org ---
Author: dominiq
Date: Sat Apr  5 12:29:27 2014
New Revision: 209153

URL: http://gcc.gnu.org/viewcvs?rev=209153&root=gcc&view=rev
Log:
2012-04-05  Dominique d'Humieres  <dominiq@lps.ens.fr>
        Jack Howarth <howarth@bromo.med.uc.edu>

    PR target/54407
    * 30_threads/condition_variable/54185.cc: Skip for darwin < 11.


Modified:
    branches/gcc-4_7-branch/libstdc++-v3/ChangeLog
   
branches/gcc-4_7-branch/libstdc++-v3/testsuite/30_threads/condition_variable/54185.cc

[Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10

[dominiq at lps dot ens.fr]

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

Dominique d'Humieres <dominiq at lps dot ens.fr> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #24 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Finally fixed.