public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] Move split-path pass next to the tracer pass
Date: Fri, 18 Dec 2015 04:04:00 -0000	[thread overview]
Message-ID: <567385D7.7040802@redhat.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 348 bytes --]


Richi noted that the two passes, which do very similar things are at 
slightly different places in the pipeline.  There really isn't a good 
reason for that.

This patch sinks the split-path pass slightly so that it's immediately 
before the tracer pass.


Bootstrapped and regression tested on x86_64-linux-gnu & installed on 
the trunk.



Jeff

[-- Attachment #2: patch --]
[-- Type: text/plain, Size: 1441 bytes --]

commit 221e081904a5cb3423a03b7f6e3173fe205f0adb
Author: law <law@138bc75d-0d04-0410-961f-82ee72b054a4>
Date:   Fri Dec 18 04:04:20 2015 +0000

    [PATCH] Move split-path pass next to the tracer pass
    
    	* passes.def: Put the split-paths pass immediately before the
    	tracer pass.
    
    git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@231800 138bc75d-0d04-0410-961f-82ee72b054a4

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index 070b2dd..bf01dfb 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,5 +1,8 @@
 2015-12-17  Jeff Law  <law@redhat.com>
 
+	* passes.def: Put the split-paths pass immediately before the
+	tracer pass.
+
 	* doc/invoke.texi (-O2 options): Remove -fsplit-paths.
 	(-O3 options): Add -fsplit-paths.
 	* gimple-ssa-split-paths.c: Include predict.h
diff --git a/gcc/passes.def b/gcc/passes.def
index 2ba8490..59114a9 100644
--- a/gcc/passes.def
+++ b/gcc/passes.def
@@ -302,10 +302,10 @@ along with GCC; see the file COPYING3.  If not see
       POP_INSERT_PASSES ()
       NEXT_PASS (pass_simduid_cleanup);
       NEXT_PASS (pass_lower_vector_ssa);
-      NEXT_PASS (pass_split_paths);
       NEXT_PASS (pass_cse_reciprocals);
       NEXT_PASS (pass_reassoc, false /* insert_powi_p */);
       NEXT_PASS (pass_strength_reduction);
+      NEXT_PASS (pass_split_paths);
       NEXT_PASS (pass_tracer);
       NEXT_PASS (pass_dominator, false /* may_peel_loop_headers_p */);
       NEXT_PASS (pass_strlen);

                 reply	other threads:[~2015-12-18  4:04 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=567385D7.7040802@redhat.com \
    --to=law@redhat.com \
    --cc=gcc-patches@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).