public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/105122] [12 Regression] Testsuite failures since r12-7931 on i686-linux
Date: Mon, 04 Apr 2022 06:41:37 +0000 [thread overview]
Message-ID: <bug-105122-4-aiLMDR53Br@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-105122-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105122
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
PASS: gcc.dg/strlenopt-73.c (test for excess errors)
gcc.dg/strlenopt-73.c: pattern found 4 times
FAIL: gcc.dg/strlenopt-73.c scan-tree-dump-times optimized "strlen" 0
gcc.dg/strlenopt-73.c: pattern found 6 times
FAIL: gcc.dg/strlenopt-73.c scan-tree-dump-times optimized "_not_eliminated_" 0
#if defined(__i386__) || defined(__x86_64__) || defined(__aarch64__) \
|| defined(__s390__) || defined(__powerpc64__)
/* The following tests assume GCC transforms the memcpy calls into
long long assignments which it does only on targets that define
the MOVE_MAX macro to 8 or higher. Enable on a set of targets
known to do that. */
that's no longer true for i?86 w/o SSE (and now memcpy folding honors that).
I'll adjust this testcase.
PASS: gcc.dg/strlenopt-80.c (test for excess errors)
gcc.dg/strlenopt-80.c: pattern found 5 times
FAIL: gcc.dg/strlenopt-80.c scan-tree-dump-times optimized "failure_on_line
\\(" 0
similar, the testcase says
The optimization is only implemented for MEM_REF stores and other
targets than those below may not transform the memcpy call into
such a store.
{ dg-do compile { target { { aarch64*-*-* i?86-*-* x86_64-*-* } || { {
powerpc*-*-* } && lp64 } } } }
one way to fix this testcase would be to explicitely enable SSE for i?86-*-*.
next prev parent reply other threads:[~2022-04-04 6:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 10:29 [Bug target/105122] New: " jakub at gcc dot gnu.org
2022-04-01 10:29 ` [Bug target/105122] " jakub at gcc dot gnu.org
2022-04-01 12:08 ` rguenth at gcc dot gnu.org
2022-04-01 12:41 ` rguenth at gcc dot gnu.org
2022-04-04 6:41 ` rguenth at gcc dot gnu.org [this message]
2022-04-06 6:15 ` cvs-commit at gcc dot gnu.org
2022-04-06 6:15 ` 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-105122-4-aiLMDR53Br@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).