This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10
- From: "howarth at nitro dot med.uc.edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sun, 14 Oct 2012 20:53:56 +0000
- Subject: [Bug target/54407] FAIL: 30_threads/condition_variable/54185.cc execution test program timed out on powerpc-apple-darwin9 and x86_64-apple-darwin10
- Auto-submitted: auto-generated
- References: <bug-54407-4@http.gcc.gnu.org/bugzilla/>
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.