From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26489 invoked by alias); 3 Feb 2014 16:05:33 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 26416 invoked by uid 48); 3 Feb 2014 16:05:28 -0000 From: "ro at gcc dot 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 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ro at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cf_gcctarget cc cf_gcchost cf_gccbuild Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-02/txt/msg00165.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59305 Rainer Orth 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 --- 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