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/102789] New: [12 regression] libgomp.c++/simd-3.C fails after r12-xxxx for 32 bits
Date: Fri, 15 Oct 2021 20:09:18 +0000 [thread overview]
Message-ID: <bug-102789-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102789
Bug ID: 102789
Summary: [12 regression] libgomp.c++/simd-3.C fails after
r12-xxxx for 32 bits
Product: gcc
Version: 12.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:fab2f61dc1b195fec9161be15635b87d312e4626, r12-4340
make -k check-target-libgomp RUNTESTFLAGS="--target_board=unix'{-m32}'
c++.exp=libgomp.c++/simd-3.C"
FAIL: libgomp.c++/simd-3.C execution test
# of expected passes 1
# of unexpected failures 1
I couldn't get a traceback of where it failed other than it was in main.
commit fab2f61dc1b195fec9161be15635b87d312e4626
Author: Jakub Jelinek <jakub@redhat.com>
Date: Tue Oct 12 09:28:10 2021 +0200
vectorizer: Fix up -fsimd-cost-model= handling
next reply other threads:[~2021-10-15 20:09 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 20:09 seurer at gcc dot gnu.org [this message]
2021-10-15 20:10 ` [Bug libgomp/102789] " seurer at gcc dot gnu.org
2021-10-18 6:29 ` [Bug libgomp/102789] [12 regression] libgomp.c++/simd-3.C fails after r12-4340 " rguenth at gcc dot gnu.org
2021-10-18 10:05 ` [Bug target/102789] " jakub at gcc dot gnu.org
2021-10-18 10:20 ` jakub at gcc dot gnu.org
2021-10-19 6:51 ` linkw at gcc dot gnu.org
2021-10-20 6:24 ` linkw at gcc dot gnu.org
2021-10-25 3:08 ` linkw at gcc dot gnu.org
2021-10-26 3:18 ` cvs-commit at gcc dot gnu.org
2021-10-26 3:21 ` [Bug tree-optimization/102789] " linkw at gcc dot gnu.org
2021-10-26 3:28 ` linkw at gcc dot gnu.org
2021-11-05 13:57 ` [Bug tree-optimization/102789] " rguenth at gcc dot gnu.org
2021-11-05 14:00 ` jakub at gcc dot gnu.org
2021-11-08 5:31 ` cvs-commit at gcc dot gnu.org
2021-11-08 5:33 ` cvs-commit at gcc dot gnu.org
2021-11-08 5:34 ` cvs-commit at gcc dot gnu.org
2021-11-08 5:36 ` linkw 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-102789-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).