public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/113005] New: 'libgomp.fortran/rwlock_1.f90', 'libgomp.fortran/rwlock_3.f90' execution test timeouts
Date: Wed, 13 Dec 2023 20:46:45 +0000 [thread overview]
Message-ID: <bug-113005-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113005
Bug ID: 113005
Summary: 'libgomp.fortran/rwlock_1.f90',
'libgomp.fortran/rwlock_3.f90' execution test timeouts
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: testsuite-fail
Severity: normal
Priority: P3
Component: libfortran
Assignee: unassigned at gcc dot gnu.org
Reporter: tschwinge at gcc dot gnu.org
CC: hjl at gcc dot gnu.org
Target Milestone: ---
Target: powerpc64le-linux-gnu
On several of our "big iron" powerpc64le-linux-gnu systems, I'm seeing the new
test cases 'libgomp.fortran/rwlock_1.f90', 'libgomp.fortran/rwlock_3.f90' run
into execution test timeouts (300 s). Those were added in commit
r14-6425-gb806c88fab3f9c6833563f9a44b608dd5dd14de9 "libgfortran: Replace mutex
with rwlock".
PASS: libgomp.fortran/rwlock_1.f90 -O0 (test for excess errors)
WARNING: program timed out.
FAIL: libgomp.fortran/rwlock_1.f90 -O0 execution test
PASS: libgomp.fortran/rwlock_1.f90 -O1 (test for excess errors)
WARNING: program timed out.
FAIL: libgomp.fortran/rwlock_1.f90 -O1 execution test
PASS: libgomp.fortran/rwlock_1.f90 -O2 (test for excess errors)
WARNING: program timed out.
FAIL: libgomp.fortran/rwlock_1.f90 -O2 execution test
PASS: libgomp.fortran/rwlock_1.f90 -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess
errors)
WARNING: program timed out.
FAIL: libgomp.fortran/rwlock_1.f90 -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions execution test
PASS: libgomp.fortran/rwlock_1.f90 -O3 -g (test for excess errors)
WARNING: program timed out.
FAIL: libgomp.fortran/rwlock_1.f90 -O3 -g execution test
PASS: libgomp.fortran/rwlock_1.f90 -Os (test for excess errors)
WARNING: program timed out.
FAIL: libgomp.fortran/rwlock_1.f90 -Os execution test
PASS: libgomp.fortran/rwlock_2.f90 -O0 (test for excess errors)
PASS: libgomp.fortran/rwlock_2.f90 -O0 execution test
PASS: libgomp.fortran/rwlock_2.f90 -O1 (test for excess errors)
PASS: libgomp.fortran/rwlock_2.f90 -O1 execution test
PASS: libgomp.fortran/rwlock_2.f90 -O2 (test for excess errors)
PASS: libgomp.fortran/rwlock_2.f90 -O2 execution test
PASS: libgomp.fortran/rwlock_2.f90 -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess
errors)
PASS: libgomp.fortran/rwlock_2.f90 -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions execution test
PASS: libgomp.fortran/rwlock_2.f90 -O3 -g (test for excess errors)
PASS: libgomp.fortran/rwlock_2.f90 -O3 -g execution test
PASS: libgomp.fortran/rwlock_2.f90 -Os (test for excess errors)
PASS: libgomp.fortran/rwlock_2.f90 -Os execution test
PASS: libgomp.fortran/rwlock_3.f90 -O0 (test for excess errors)
WARNING: program timed out.
FAIL: libgomp.fortran/rwlock_3.f90 -O0 execution test
PASS: libgomp.fortran/rwlock_3.f90 -O1 (test for excess errors)
WARNING: program timed out.
FAIL: libgomp.fortran/rwlock_3.f90 -O1 execution test
PASS: libgomp.fortran/rwlock_3.f90 -O2 (test for excess errors)
WARNING: program timed out.
FAIL: libgomp.fortran/rwlock_3.f90 -O2 execution test
PASS: libgomp.fortran/rwlock_3.f90 -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions (test for excess
errors)
WARNING: program timed out.
FAIL: libgomp.fortran/rwlock_3.f90 -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions execution test
PASS: libgomp.fortran/rwlock_3.f90 -O3 -g (test for excess errors)
WARNING: program timed out.
FAIL: libgomp.fortran/rwlock_3.f90 -O3 -g execution test
PASS: libgomp.fortran/rwlock_3.f90 -Os (test for excess errors)
WARNING: program timed out.
FAIL: libgomp.fortran/rwlock_3.f90 -Os execution test
All-PASS on all x86_64-pc-linux-gnu systems that I've tested.
next reply other threads:[~2023-12-13 20:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-13 20:46 tschwinge at gcc dot gnu.org [this message]
2023-12-21 11:41 ` [Bug testsuite/113005] " tschwinge at gcc dot gnu.org
2023-12-21 11:47 ` jakub at gcc dot gnu.org
2023-12-21 11:50 ` jakub at gcc dot gnu.org
2023-12-22 6:52 ` lipeng.zhu at intel dot com
2023-12-22 8:48 ` jakub at gcc dot gnu.org
2023-12-22 8:59 ` jakub at gcc dot gnu.org
2023-12-22 9:02 ` jakub at gcc dot gnu.org
2023-12-22 9:04 ` jakub at gcc dot gnu.org
2023-12-22 9:59 ` lipeng.zhu at intel dot com
2023-12-22 11:14 ` jakub at gcc dot gnu.org
2023-12-25 2:55 ` lipeng.zhu at intel dot com
2023-12-25 6:22 ` lipeng.zhu at intel dot com
2023-12-25 7:31 ` lipeng.zhu at intel dot com
2024-01-22 1:02 ` lipeng.zhu at intel dot com
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-113005-4@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).