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 tree-optimization/109048] [13 regression] redundant mask compare generated by vectorizer.
Date: Mon, 27 Mar 2023 10:37:36 +0000 [thread overview]
Message-ID: <bug-109048-4-v2L7yUOCEP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109048-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109048
--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #8)
> Created attachment 54762 [details]
> heuristic
>
> I am testing this heuristic
FAIL: gcc.dg/tree-ssa/ranger-threader-3.c scan-tree-dump-times ethread
"Register
ing.*jump thread" 1
FAIL: gcc.dg/tree-ssa/ssa-dom-thread-14.c scan-tree-dump-times dom2 "Threaded"
2
is the fallout - both are the same testcase, both can be mitigated by adjusting
the dump to scan for and making sure PROP_loop_opts_done is also provided
for functions without loops.
But it also shows a case where we optimize things significantly later
after the change.
if ((!unsignedp || (!left && methods == OPTAB_WIDEN)))
{
enum optab_methods methods1 = methods;
if (unsignedp)
methods1 = OPTAB_MUST_WIDEN;
expand_binop (left ? lshift_optab : rshift_arith_optab,
unsignedp, methods1);
used to be threaded in early threading but now would be delayed to after
loop opts.
next prev parent reply other threads:[~2023-03-27 10:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-07 6:01 [Bug tree-optimization/109048] New: " crazylht at gmail dot com
2023-03-07 6:03 ` [Bug tree-optimization/109048] " crazylht at gmail dot com
2023-03-07 6:13 ` crazylht at gmail dot com
2023-03-07 6:22 ` crazylht at gmail dot com
2023-03-07 6:34 ` crazylht at gmail dot com
2023-03-07 9:17 ` rguenth at gcc dot gnu.org
2023-03-07 9:38 ` jakub at gcc dot gnu.org
2023-03-07 10:09 ` rguenther at suse dot de
2023-03-27 8:26 ` rguenth at gcc dot gnu.org
2023-03-27 9:18 ` rguenth at gcc dot gnu.org
2023-03-27 10:37 ` rguenth at gcc dot gnu.org [this message]
2023-03-28 12:20 ` rguenth at gcc dot gnu.org
2023-04-13 7:30 ` rguenth at gcc dot gnu.org
2023-04-13 8:14 ` crazylht at gmail dot com
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-109048-4-v2L7yUOCEP@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).