public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Aldy Hernandez <aldyh@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-4495] Change threading comment before pass_ccp pass. Date: Tue, 19 Oct 2021 08:48:54 +0000 (GMT) [thread overview] Message-ID: <20211019084854.1A00C385840C@sourceware.org> (raw) https://gcc.gnu.org/g:d2161caffbb56a434776608af4e4491b59e508c8 commit r12-4495-gd2161caffbb56a434776608af4e4491b59e508c8 Author: Aldy Hernandez <aldyh@redhat.com> Date: Tue Oct 19 09:33:34 2021 +0200 Change threading comment before pass_ccp pass. gcc/ChangeLog: * passes.def: Change threading comment before pass_ccp pass. Diff: --- gcc/passes.def | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/gcc/passes.def b/gcc/passes.def index c11c237f6d2..4c54176328b 100644 --- a/gcc/passes.def +++ b/gcc/passes.def @@ -339,9 +339,7 @@ along with GCC; see the file COPYING3. If not see NEXT_PASS (pass_thread_jumps); NEXT_PASS (pass_vrp, false /* warn_array_bounds_p */); NEXT_PASS (pass_vrp_threader); - /* Threading can leave many const/copy propagations in the IL. - Clean them up. Instead of just copy_prop, we use ccp to - compute alignment and nonzero bits. */ + /* Run CCP to compute alignment and nonzero bits. */ NEXT_PASS (pass_ccp, true /* nonzero_p */); NEXT_PASS (pass_warn_restrict); NEXT_PASS (pass_dse);
reply other threads:[~2021-10-19 8:48 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=20211019084854.1A00C385840C@sourceware.org \ --to=aldyh@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).