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/99626] New: [10/11 regression] gcc.dg/strlenopt-73.c fails for 32 bits
Date: Wed, 17 Mar 2021 14:18:39 +0000 [thread overview]
Message-ID: <bug-99626-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99626
Bug ID: 99626
Summary: [10/11 regression] gcc.dg/strlenopt-73.c fails for 32
bits
Product: gcc
Version: 11.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: ---
This is an old one but I don't see a PR for it. Note that PR91449 fixed this
for 64 bit.
g:34fcf41e30ff56155e996f5e04f6ca13948a19b6, r10-2528
make -k check-gcc RUNTESTFLAGS="--target_board=unix'{-m32}'
dg.exp=gcc.dg/strlenopt-73.c"
FAIL: gcc.dg/strlenopt-73.c scan-tree-dump-times optimized "strlen" 0
FAIL: gcc.dg/strlenopt-73.c scan-tree-dump-times optimized "_not_eliminated_" 0
# of expected passes 1
# of unexpected failures 2
The revision is where the test case was added in gcc 10 and it still fails for
32 bits on powerpc64 BE now in both gcc 10 and trunk.
commit 34fcf41e30ff56155e996f5e04f6ca13948a19b6
Author: Martin Sebor <msebor@redhat.com>
Date: Wed Aug 14 16:27:59 2019 +0000
PR tree-optimization/91294 - [10 Regression] wrong strlen result of a
conditional with an offset
next reply other threads:[~2021-03-17 14:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-17 14:18 seurer at gcc dot gnu.org [this message]
2021-03-17 15:33 ` [Bug testsuite/99626] " rguenth at gcc dot gnu.org
2021-03-17 15:34 ` jakub at gcc dot gnu.org
2021-03-18 15:14 ` cvs-commit at gcc dot gnu.org
2021-03-18 15:22 ` [Bug testsuite/99626] [10 Regression] " jakub at gcc dot gnu.org
2021-03-19 23:30 ` cvs-commit at gcc dot gnu.org
2021-03-20 8:10 ` 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-99626-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).