public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Giuliano Belinassi <giulianob@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc/devel/autopar_devel] Fix streamer desynchornization caused by streamer debugging patch
Date: Sat, 22 Aug 2020 21:42:46 +0000 (GMT)	[thread overview]
Message-ID: <20200822214246.96BD53850418@sourceware.org> (raw)

https://gcc.gnu.org/g:88a7791d41c0d9dda7c78d7f48c6f9c2b12db624

commit 88a7791d41c0d9dda7c78d7f48c6f9c2b12db624
Author: Jan Hubicka <jh@suse.cz>
Date:   Fri May 29 12:25:48 2020 +0200

    Fix streamer desynchornization caused by streamer debugging patch
    
    it turns out I lost one hunk in the patch disabling extra streaming
    which causes streamer to go out of sync in the case non-trivial scc
    containing the node being streamed appears in local stream (which seems
    quite rare since it does not happen during bootstrap).
    
    2020-05-29  Jan Hubicka  <hubicka@ucw.cz>
    
            PR lto/95362
            * lto-streamer-out.c (lto_output_tree): Disable redundant streaming.

Diff:
---
 gcc/lto-streamer-out.c | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/gcc/lto-streamer-out.c b/gcc/lto-streamer-out.c
index 288e3c0f4c6..dfd32ece4bd 100644
--- a/gcc/lto-streamer-out.c
+++ b/gcc/lto-streamer-out.c
@@ -1791,8 +1791,9 @@ lto_output_tree (struct output_block *ob, tree expr,
 	    }
 	  streamer_write_record_start (ob, LTO_tree_pickle_reference);
 	  streamer_write_uhwi (ob, ix);
-	  streamer_write_enum (ob->main_stream, LTO_tags, LTO_NUM_TAGS,
-			       lto_tree_code_to_tag (TREE_CODE (expr)));
+	  if (streamer_debugging)
+	    streamer_write_enum (ob->main_stream, LTO_tags, LTO_NUM_TAGS,
+				 lto_tree_code_to_tag (TREE_CODE (expr)));
 	}
       in_dfs_walk = false;
       lto_stats.num_pickle_refs_output++;


                 reply	other threads:[~2020-08-22 21:42 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=20200822214246.96BD53850418@sourceware.org \
    --to=giulianob@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: 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).