public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: "Martin Liška" <mliska@suse.cz>
Cc: Xiong Hu Luo <luoxhu@linux.ibm.com>,
	gcc-patches@gcc.gnu.org,        hubicka@ucw.cz,
	wschmidt@linux.ibm.com
Subject: Re: [PATCH v2] Generalize get_most_common_single_value to return k_th value & count
Date: Mon, 15 Jul 2019 14:41:00 -0000	[thread overview]
Message-ID: <20190715143124.GD20882@gate.crashing.org> (raw)
In-Reply-To: <20155b46-2d75-0902-a864-1740c1fd8762@suse.cz>

On Mon, Jul 15, 2019 at 04:23:18PM +0200, Martin Liška wrote:
> On 7/15/19 4:17 PM, Segher Boessenkool wrote:
> > Is that enough?  Can there be two entries with the same count as well
> > as value?
> 
> Yes, it can happen very unlikely in a multi-threaded instrumentation,
> but it will not make a problem.

It will result in different sort order on different hosts, then.  Is
that okay here?  Does a different order here not lead to different
compiler output?

(Consider the case where you copied the data files between hosts).


Segher

  reply	other threads:[~2019-07-15 14:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-15  8:50 Xiong Hu Luo
2019-07-15 10:36 ` Martin Liška
2019-07-15 14:23   ` Segher Boessenkool
2019-07-15 14:31     ` Martin Liška
2019-07-15 14:41       ` Segher Boessenkool [this message]
2019-07-15 14:44         ` Martin Liška
2019-07-15 15:28           ` Segher Boessenkool
2019-07-16  7:42   ` [PATCH v3] " luoxhu
2019-07-16 10:34     ` Martin Liška
2019-07-17  6:02       ` [PATCH v4] " luoxhu
2019-07-17  8:05         ` Martin Liška
2019-07-17  8:46           ` luoxhu
2019-07-17  9:23             ` Martin Liška
2019-07-24 18:57           ` Jeff Law

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=20190715143124.GD20882@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hubicka@ucw.cz \
    --cc=luoxhu@linux.ibm.com \
    --cc=mliska@suse.cz \
    --cc=wschmidt@linux.ibm.com \
    /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).