public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jiu Fu Guo <guojiufu@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/vendors/ibm/heads/perf)] Restore LTO PGO bootstrap after ea0b12523d0d9a9059b5.
Date: Thu, 19 Mar 2020 05:39:40 +0000 (GMT)	[thread overview]
Message-ID: <20200319053940.A8A373944422@sourceware.org> (raw)

https://gcc.gnu.org/g:fa1160f6e50500aa38162fefb43bfb10c25e0363

commit fa1160f6e50500aa38162fefb43bfb10c25e0363
Author: Martin Liska <mliska@suse.cz>
Date:   Tue Feb 18 16:33:44 2020 +0100

    Restore LTO PGO bootstrap after ea0b12523d0d9a9059b5.
    
            * value-prof.c (stream_out_histogram_value): Restore LTO PGO
            bootstrap by missing removal of invalid sanity check.

Diff:
---
 gcc/ChangeLog    | 5 +++++
 gcc/value-prof.c | 2 +-
 2 files changed, 6 insertions(+), 1 deletion(-)

diff --git a/gcc/ChangeLog b/gcc/ChangeLog
index c107f19a0f4..731bae4bbda 100644
--- a/gcc/ChangeLog
+++ b/gcc/ChangeLog
@@ -1,3 +1,8 @@
+2020-02-18  Martin Liska  <mliska@suse.cz>
+
+	* value-prof.c (stream_out_histogram_value): Restore LTO PGO
+	bootstrap by missing removal of invalid sanity check.
+
 2020-02-18  Martin Liska  <mliska@suse.cz>
 
 	PR ipa/92518
diff --git a/gcc/value-prof.c b/gcc/value-prof.c
index 5f940f40399..8e9f129708a 100644
--- a/gcc/value-prof.c
+++ b/gcc/value-prof.c
@@ -332,7 +332,7 @@ stream_out_histogram_value (struct output_block *ob, histogram_value hist)
       /* When user uses an unsigned type with a big value, constant converted
 	 to gcov_type (a signed type) can be negative.  */
       gcov_type value = hist->hvalue.counters[i];
-      if (hist->type == HIST_TYPE_TOPN_VALUES && i > 0)
+      if (hist->type == HIST_TYPE_TOPN_VALUES)
 	;
       else
 	gcc_assert (value >= 0);


                 reply	other threads:[~2020-03-19  5: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=20200319053940.A8A373944422@sourceware.org \
    --to=guojiufu@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).