public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Jan Hubicka <hubicka@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc(refs/users/kubaneko/heads/histogram)] Clear profile in vectorizer. Date: Mon, 1 May 2023 22:39:51 +0000 (GMT) [thread overview] Message-ID: <20230501223951.B6AFA3858D1E@sourceware.org> (raw) https://gcc.gnu.org/g:8667da401c2968aab100c355c89e044b95314aca commit 8667da401c2968aab100c355c89e044b95314aca Author: Honza <jh@ryzen3.suse.cz> Date: Tue May 2 00:39:34 2023 +0200 Clear profile in vectorizer. Diff: --- gcc/tree-vect-loop-manip.cc | 6 ++++++ gcc/tree-vect-loop.cc | 3 +++ 2 files changed, 9 insertions(+) diff --git a/gcc/tree-vect-loop-manip.cc b/gcc/tree-vect-loop-manip.cc index 6aa3d2ed0bf..8eb2942b847 100644 --- a/gcc/tree-vect-loop-manip.cc +++ b/gcc/tree-vect-loop-manip.cc @@ -2941,6 +2941,10 @@ vect_do_peeling (loop_vec_info loop_vinfo, tree niters, tree nitersm1, /* Prolog iterates at most bound_prolog times, latch iterates at most bound_prolog - 1 times. */ record_niter_bound (prolog, bound_prolog - 1, false, true); + /* TODO: Update counters or at least release vectors. + We do not produce prologs on modern x86 targets we test on + so this is not important for proof of concept. */ + prolog->counters = NULL; delete_update_ssa (); adjust_vec_debug_stmts (); scev_reset (); @@ -3077,6 +3081,8 @@ vect_do_peeling (loop_vec_info loop_vinfo, tree niters, tree nitersm1, /* -1 to convert loop iterations to latch iterations. */ record_niter_bound (epilog, bound - 1, false, true); } + /* TODO: Compute epilog histograms or at least release the counters. */ + epilog->counters = NULL; delete_update_ssa (); adjust_vec_debug_stmts (); diff --git a/gcc/tree-vect-loop.cc b/gcc/tree-vect-loop.cc index ba068af264c..928079a7c9b 100644 --- a/gcc/tree-vect-loop.cc +++ b/gcc/tree-vect-loop.cc @@ -11139,6 +11139,9 @@ vect_transform_loop (loop_vec_info loop_vinfo, gimple *loop_vectorized_call) assumed_vf) - 1 : wi::udiv_floor (loop->nb_iterations_estimate + bias_for_assumed, assumed_vf) - 1); + /* TODO: Fix profile after vectorization. */ + if (loop->counters) + loop->counters = NULL; if (dump_enabled_p ()) {
reply other threads:[~2023-05-01 22:39 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230501223951.B6AFA3858D1E@sourceware.org \ --to=hubicka@gcc.gnu.org \ --cc=gcc-cvs@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: linkBe 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).