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 testsuite/108985] New: new test case gcc.dg/vect/pr108950.c from r13-6384-ge3837b6f6c28a1 fails
Date: Wed, 01 Mar 2023 15:51:48 +0000 [thread overview]
Message-ID: <bug-108985-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108985
Bug ID: 108985
Summary: new test case gcc.dg/vect/pr108950.c from
r13-6384-ge3837b6f6c28a1 fails
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
Tried g:e3837b6f6c28a1d2cea3a69efbda795ea3fb8816, r13-6384-ge3837b6f6c28a1
make -k check-gcc RUNTESTFLAGS="vect.exp=gcc.dg/vect/pr108950.c"
# of expected passes 2
# of unresolved testcases 2
spawn -ignore SIGHUP /home/seurer/gcc/git/build/gcc-test/gcc/xgcc
-B/home/seurer/gcc/git/build/gcc-test/gcc/
/home/seurer/gcc/git/gcc-test/gcc/testsuite/gcc.dg/vect/pr108950.c
-fdiagnostics-plain-output -maltivec -mpower9-vector -ftree-vectorize
-fno-tree-loop-distribute-patterns -fno-vect-cost-model -fno-common -O2
-fdump-tree-vect-details -S -o pr108950.s^M
PASS: gcc.dg/vect/pr108950.c (test for excess errors)
gcc.dg/vect/pr108950.c: dump file does not exist
UNRESOLVED: gcc.dg/vect/pr108950.c scan-tree-dump-not vect "widen_sum"
commit e3837b6f6c28a1d2cea3a69efbda795ea3fb8816 (HEAD)
Author: Richard Biener <rguenther@suse.de>
Date: Tue Feb 28 15:34:27 2023 +0100
tree-optimization/108950 - widen-sum reduction ICE
next reply other threads:[~2023-03-01 15:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 15:51 seurer at gcc dot gnu.org [this message]
2023-03-02 8:05 ` [Bug testsuite/108985] " cvs-commit at gcc dot gnu.org
2023-03-02 8:05 ` rguenth at gcc dot gnu.org
2023-03-16 7:23 ` cvs-commit at gcc dot gnu.org
2023-05-10 6:55 ` cvs-commit 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-108985-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).