Comment # 4 on bug 1202027 from Martin Li������ka

(In reply to Richard Biener from comment #3)
> dumping with -l shows additional (a lot of) differences:
> 
> @@ -1,7 +1,7 @@
>  gimple-match.gcda:data:magic `gcda':version `B21*'
> -gimple-match.gcda:stamp 1483659858
> +gimple-match.gcda:stamp 1483764244
>  gimple-match.gcda:checksum 2047081074
> -gimple-match.gcda:  a1000000:   8:OBJECT_SUMMARY runs=2417,
> sum_max=3967228784
> +gimple-match.gcda:  a1000000:   8:OBJECT_SUMMARY runs=2417,
> sum_max=3967227559
>  gimple-match.gcda:  01000000:  12:FUNCTION ident=791600706,
> lineno_checksum=0x29e79d07, cfg_checksum=0xdb3053ac
>  gimple-match.gcda:    01a10000:  24:COUNTERS arcs 3 counts (all zero)
>  gimple-match.gcda:                   0: 0 0 0 
> @@ -2240,24 +2240,24 @@
>  gimple-match.gcda:                  104: 887567714 77 77 1 887567714 77 552
> 3 
>  gimple-match.gcda:                  112: 887567714 544 254370539 6
> 806698082 2 552 3 
>  gimple-match.gcda:                  120: 887567714 544 254370539 6
> 806698082 2 8724 8 
> -gimple-match.gcda:                  128: 887567714 7033 806698082 305
> 254370539 1294 1597189827 20 
> +gimple-match.gcda:                  128: 806698082 305 887567714 7033
> 254370539 1294 1597189827 20 
> 
> and more like this.

Well, these are actually indirect_call counters of the following format:
(fn_id, fn_count) and these are only in a different order. When a profile is
used we sort it by fn_count.

But the sum_max difference means there are differences in arc counters as well.
Let me find that..