public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/108601] [13 Regression] vector peeling ICEs with PGO + LTO + IPA inlining in gcc_r in SPEC2017
Date: Tue, 31 Jan 2023 08:28:34 +0000 [thread overview]
Message-ID: <bug-108601-4-q5xDd7oVYZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108601-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108601
--- Comment #5 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to Hongtao.liu from comment #4)
> So that would be case: the tripcount is known, the vect_factor is known, but
> still niters_vector_mult_vf is variable(or it's not fold into an constant).?
Maybe related to this tricky
if (!integer_onep (*step_vector))
{
/* On exit from the loop we will have an easy way of calcalating
NITERS_VECTOR / STEP * STEP. Install a dummy definition
until then. */
niters_vector_mult_vf = make_ssa_name (TREE_TYPE (*niters_vector));
SSA_NAME_DEF_STMT (niters_vector_mult_vf) = gimple_build_nop ();
*niters_vector_mult_vf_var = niters_vector_mult_vf;
}
else
vect_gen_vector_loop_niters_mult_vf (loop_vinfo, *niters_vector,
&niters_vector_mult_vf);
next prev parent reply other threads:[~2023-01-31 8:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 15:43 [Bug tree-optimization/108601] New: " tnfchris at gcc dot gnu.org
2023-01-30 16:05 ` [Bug tree-optimization/108601] " pinskia at gcc dot gnu.org
2023-01-31 7:25 ` rguenth at gcc dot gnu.org
2023-01-31 7:29 ` rguenth at gcc dot gnu.org
2023-01-31 7:49 ` crazylht at gmail dot com
2023-01-31 8:28 ` crazylht at gmail dot com [this message]
2023-01-31 9:05 ` tnfchris at gcc dot gnu.org
2023-01-31 20:24 ` [Bug tree-optimization/108601] [13 Regression] vector peeling ICEs with VLA in gcc_r in SPEC2017 since g:c13223b790bbc5e4a3f5605e057eac59b61b2c85 tnfchris at gcc dot gnu.org
2023-01-31 21:08 ` tnfchris at gcc dot gnu.org
2023-02-01 5:32 ` crazylht at gmail dot com
2023-02-01 7:29 ` crazylht at gmail dot com
2023-02-01 7:32 ` rguenther at suse dot de
2023-02-01 7:46 ` crazylht at gmail dot com
2023-02-01 8:41 ` rguenth at gcc dot gnu.org
2023-02-01 9:07 ` crazylht at gmail dot com
2023-02-02 9:02 ` cvs-commit at gcc dot gnu.org
2023-02-03 8:05 ` 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-108601-4-q5xDd7oVYZ@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).