public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
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
Date: Sun, 14 Oct 2012 21:18:00 -0000 [thread overview]
Message-ID: <bug-54407-4-C83woRY1Mz@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-54407-4@http.gcc.gnu.org/bugzilla/>
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?
next prev parent reply other threads:[~2012-10-14 21:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 13:36 [Bug target/54407] New: " dominiq at lps dot ens.fr
2012-08-30 10:42 ` [Bug target/54407] " redi at gcc dot gnu.org
2012-08-30 12:54 ` dominiq at lps dot ens.fr
2012-08-30 16:41 ` redi at gcc dot gnu.org
2012-10-14 17:08 ` dominiq at lps dot ens.fr
2012-10-14 18:35 ` howarth at nitro dot med.uc.edu
2012-10-14 19:06 ` dominiq at lps dot ens.fr
2012-10-14 20:14 ` howarth at nitro dot med.uc.edu
2012-10-14 20:48 ` dominiq at lps dot ens.fr
2012-10-14 20:54 ` howarth at nitro dot med.uc.edu
2012-10-14 21:12 ` howarth at nitro dot med.uc.edu
2012-10-14 21:13 ` howarth at nitro dot med.uc.edu
2012-10-14 21:18 ` dominiq at lps dot ens.fr [this message]
2012-10-14 21:23 ` howarth at nitro dot med.uc.edu
2012-10-14 21:35 ` dominiq at lps dot ens.fr
2012-10-14 22:17 ` howarth at nitro dot med.uc.edu
2012-10-16 10:07 ` redi at gcc dot gnu.org
2013-03-10 17:58 ` dominiq at lps dot ens.fr
2013-03-11 14:51 ` howarth at nitro dot med.uc.edu
2013-06-29 15:47 ` dominiq at lps dot ens.fr
2013-06-29 20:29 ` paolo.carlini at oracle dot com
2014-04-02 8:45 ` dominiq at gcc dot gnu.org
2014-04-05 12:26 ` dominiq at gcc dot gnu.org
2014-04-05 12:30 ` dominiq at gcc dot gnu.org
2014-04-05 12:33 ` dominiq at lps dot ens.fr
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-54407-4-C83woRY1Mz@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).