public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/59305] [4.9 Regression] gcc.dg/atomic/c11-atomic-exec-5.c fails with WARNING: program timed out on x86_64-apple-darwin13
Date: Mon, 03 Feb 2014 16:05:00 -0000	[thread overview]
Message-ID: <bug-59305-4-lsnR28cR0U@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59305-4@http.gcc.gnu.org/bugzilla/>

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

Rainer Orth <ro at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|x86_64-apple-darwin13       |x86_64-apple-darwin13,
                   |                            |sparc-sun-solaris2.10
                 CC|                            |ro at gcc dot gnu.org
               Host|x86_64-apple-darwin13       |x86_64-apple-darwin13,
                   |                            |sparc-sun-solaris2.10
              Build|x86_64-apple-darwin13       |x86_64-apple-darwin13,
                   |                            |sparc-sun-solaris2.10

--- Comment #9 from Rainer Orth <ro at gcc dot gnu.org> ---
I see the same issue on some Solaris 10/SPARC systems on UltraSPARC T2:

The 32-bit -O0 test execution takes between an 12 min and an hour:

            yoda          apoc    mayon

real          30:46.09      11.80        39.49    
user        1:01:31.87      20.12   1:18.84
sys               0.25       1.91      0.07

The first numbers (yoda) are for 1.2 GHz UltraSPARC T2 running Solaris 10, the
second set (apoc) for 1.35 GHz UltraSPARC IV running Solaris 11, and the third
set (mayon) for 1.2 GHz UltraSPARC T2 running Solaris 11.

When I run the tests manually, I see that only a few tests are very slow:

complex_double_add_overflow, complex_double_sub_overflow,
complex_double_mul_overflow, complex_double_div_overflow, and some more.

Even if I reduce the test to just the complex_double_add_overflow case, it
takes

              yoda    mayon

real        2:04.11       0.33
user        4:08.14       0.60
sys            0.03       0.01

Timing on mayon is quite varied, though, some runs taking 12.83 s.

Running the test under plockstat to check for locking issues, the picture
changes
again:

yoda between 5.48 s and 1:10.00 min, mayon between 10.14 s and 56.27 s.

Not very conclusive yet; maybe something changes with adapting
libatomic/config/posix/lock.c (PAGE_SIZE and CACHLINE_SIZE) to values
appropriate for
Solaris/SPARC.

  Rainer


  parent reply	other threads:[~2014-02-03 16:05 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-26 17:54 [Bug target/59305] New: " howarth at nitro dot med.uc.edu
2013-11-26 18:17 ` [Bug target/59305] " dominiq at lps dot ens.fr
2013-11-27  8:57 ` [Bug target/59305] [4.9 Regression] " rguenth at gcc dot gnu.org
2013-11-27 15:58 ` joseph at codesourcery dot com
2013-12-16 20:43 ` howarth at nitro dot med.uc.edu
2013-12-16 20:44 ` howarth at nitro dot med.uc.edu
2013-12-16 20:46 ` howarth at nitro dot med.uc.edu
2013-12-16 21:13 ` dominiq at lps dot ens.fr
2013-12-17 13:32 ` dominiq at lps dot ens.fr
2013-12-17 13:54 ` dominiq at lps dot ens.fr
2014-02-03 16:05 ` ro at gcc dot gnu.org [this message]
2014-02-03 16:21 ` iains at gcc dot gnu.org
2014-02-05 14:12 ` ro at CeBiTec dot Uni-Bielefeld.DE
2014-02-05 14:56 ` iains at gcc dot gnu.org
2014-02-05 14:59 ` ro at CeBiTec dot Uni-Bielefeld.DE
2014-02-05 15:06 ` iains at gcc dot gnu.org
2014-02-05 15:11 ` ro at CeBiTec dot Uni-Bielefeld.DE
2014-02-05 18:22 ` dominiq at lps dot ens.fr
2014-02-05 18:23 ` dominiq at lps dot ens.fr
2014-03-31  9:13 ` rguenth at gcc dot gnu.org
2014-03-31  9:55 ` iains at gcc dot gnu.org
2014-03-31 10:25 ` ebotcazou at gcc dot gnu.org
2014-03-31 11:14 ` rguenth at gcc dot gnu.org
2014-04-22 11:36 ` [Bug target/59305] [4.9/4.10 " jakub at gcc dot gnu.org
2014-07-16 13:28 ` jakub at gcc dot gnu.org
2014-09-14 17:12 ` [Bug target/59305] [4.9/5 " dominiq at lps dot ens.fr
2014-10-30 10:39 ` jakub at gcc dot gnu.org
2015-06-26 19:59 ` [Bug target/59305] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:30 ` jakub at gcc dot gnu.org
2015-10-01 15:13 ` clyon at gcc dot gnu.org
2015-10-01 15:39 ` pinskia at gcc dot gnu.org
2021-05-14  9:47 ` [Bug libgcc/59305] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:06 ` rguenth at gcc dot gnu.org
2022-05-27  9:35 ` [Bug libgcc/59305] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:30 ` jakub at gcc dot gnu.org
2023-07-07 10:30 ` [Bug libgcc/59305] [11/12/13/14 " rguenth 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-59305-4-lsnR28cR0U@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).