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/106396] New: [13 regression] gcc.dg/pr23911.c fails after r13-1762-gf9d4c3b45c5ed5
Date: Thu, 21 Jul 2022 23:56:53 +0000 [thread overview]
Message-ID: <bug-106396-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106396
Bug ID: 106396
Summary: [13 regression] gcc.dg/pr23911.c fails after
r13-1762-gf9d4c3b45c5ed5
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: ---
g:f9d4c3b45c5ed5f45c8089c990dbd4e181929c3d, r13-1762-gf9d4c3b45c5ed5
make -k check-gcc RUNTESTFLAGS="dg.exp=gcc.dg/pr23911.c"
FAIL: gcc.dg/pr23911.c scan-tree-dump-times dce3 "__complex__ \\(1.0e\\+0,
0.0\\)" 2
# of expected passes 2
# of unexpected failures 1
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/pr23911.c
-fdiagnostics-plain-output -O -fdump-tree-dce3 -S -o pr23911.s
PASS: gcc.dg/pr23911.c (test for excess errors)
gcc.dg/pr23911.c: pattern found 0 times
FAIL: gcc.dg/pr23911.c scan-tree-dump-times dce3 "__complex__ \\(1.0e\\+0,
0.0\\)" 2
PASS: gcc.dg/pr23911.c scan-tree-dump-times dce3 "= b" 0
commit f9d4c3b45c5ed5f45c8089c990dbd4e181929c3d (HEAD, refs/bisect/bad)
Author: liuhongt <hongtao.liu@intel.com>
Date: Tue Jul 19 17:24:52 2022 +0800
Lower complex type move to enable vectorization for complex type
load&store.
next reply other threads:[~2022-07-21 23:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 23:56 seurer at gcc dot gnu.org [this message]
2022-07-22 3:23 ` [Bug testsuite/106396] " 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-106396-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).