public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/106894] New: [13 regression] multiple libgomp failures after r13-2545-g9f2fca56593a2b
Date: Thu, 08 Sep 2022 22:48:35 +0000 [thread overview]
Message-ID: <bug-106894-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106894
Bug ID: 106894
Summary: [13 regression] multiple libgomp failures after
r13-2545-g9f2fca56593a2b
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libgomp
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
CC: jakub at gcc dot gnu.org
Target Milestone: ---
g:9f2fca56593a2b87026b399d26adcdca90705685, r13-2545-g9f2fca56593a2b: 62
failures
FAIL: libgomp.c++/../libgomp.c-c++-common/display-affinity-1.c execution test
FAIL: libgomp.c++/../libgomp.c-c++-common/icv-6.c execution test
FAIL: libgomp.c/../libgomp.c-c++-common/display-affinity-1.c execution test
FAIL: libgomp.c/../libgomp.c-c++-common/icv-6.c execution test
FAIL: libgomp.c/affinity-2.c execution test
FAIL: libgomp.fortran/affinity1.f90 -O2 execution test
FAIL: libgomp.fortran/affinity2.f90 -O2 execution test
FAIL: libgomp.fortran/display-affinity-1.f90 -O execution test
I am not sure what the execution failures are reporting. Here are two
examples:
spawn [open ...]^M
L:00000%0>rain6p1.aus.stglabs.ibm.com <!
rain6p1.aus.stglabs.ibm.com!2339838_0x200000056990_0x0000200000056990_-000001
0-7
L:00000%0>rain6p1.aus.stglabs.ibm.com <!
rain6p1.aus.stglabs.ibm.com!2339838_0x200000056990_0x0000200000056990_-000001
0-7
%000000001
FAIL: libgomp.c++/../libgomp.c-c++-common/display-affinity-1.c execution test
spawn [open ...]^M
omp_get_num_places () == 3
place 0 { 6 7 }
place 1 { 4 5 }
place 2 { 0 1 }
place 0
partition 0 - 2
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
#0 0x2000000604a7 in ???
#1 0x2000004b65ac in gomp_team_start
at /home/seurer/gcc/git/gcc-test/libgomp/team.c:382
#2 0x2000004aa787 in GOMP_parallel
at /home/seurer/gcc/git/gcc-test/libgomp/parallel.c:176
#3 0x100015fb in ???
#4 0x10000fa3 in ???
#5 0x200000589de7 in ???
#6 0x200000589fd3 in ???
#7 0xffffffffffffffff in ???
FAIL: libgomp.fortran/affinity1.f90 -O2 execution test
commit 9f2fca56593a2b87026b399d26adcdca90705685 (HEAD, refs/bisect/bad)
Author: Marcel Vollweiler <marcel@codesourcery.com>
Date: Thu Sep 8 10:01:33 2022 -0700
OpenMP, libgomp: Environment variable syntax extension
next reply other threads:[~2022-09-08 22:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 22:48 seurer at gcc dot gnu.org [this message]
2022-09-09 7:41 ` [Bug libgomp/106894] " rguenth at gcc dot gnu.org
2022-09-09 11:34 ` jakub at gcc dot gnu.org
2022-09-09 11:47 ` cvs-commit at gcc dot gnu.org
2022-09-09 11:51 ` jakub at gcc dot gnu.org
2022-09-09 12:45 ` marcel at codesourcery dot com
2022-09-09 14:55 ` jakub at gcc dot gnu.org
2022-09-09 14:55 ` jakub at gcc dot gnu.org
2022-09-12 8:49 ` cvs-commit at gcc dot gnu.org
2022-09-12 9:14 ` jakub 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-106894-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).