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 other/106575] New: new test case gcc.dg/fold-eqandshift-4.c fails
Date: Wed, 10 Aug 2022 03:48:28 +0000 [thread overview]
Message-ID: <bug-106575-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106575
Bug ID: 106575
Summary: new test case gcc.dg/fold-eqandshift-4.c fails
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
g:6fc14f1963dfefead588a4cd8902d641ed69255c, r13-2005-g6fc14f1963dfef
make -k check-gcc RUNTESTFLAGS="dg.exp=gcc.dg/fold-eqandshift-4.c"
FAIL: gcc.dg/fold-eqandshift-4.c scan-tree-dump-times optimized "return [01]"
14
FAIL: gcc.dg/fold-eqandshift-4.c scan-tree-dump-times optimized
"x_[0-9]\\(D\\)" 18
# of expected passes 6
# of unexpected failures 2
commit 6fc14f1963dfefead588a4cd8902d641ed69255c (HEAD, refs/bisect/bad)
Author: Roger Sayle <roger@nextmovesoftware.com>
Date: Tue Aug 9 18:54:43 2022 +0100
middle-end: Optimize ((X >> C1) & C2) != C3 for more cases.
next reply other threads:[~2022-08-10 3:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 3:48 seurer at gcc dot gnu.org [this message]
2022-08-10 6:08 ` [Bug other/106575] new test case gcc.dg/fold-eqandshift-4.c fails with its introduction in r13-2005-g6fc14f1963dfef cvs-commit at gcc dot gnu.org
2022-08-10 7:25 ` rguenth 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-106575-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).