On Thu, Jun 6, 2019 at 10:23 AM Martin Liška wrote:
>
> On 6/5/19 3:49 PM, Richard Biener wrote:
> > On Tue, Jun 4, 2019 at 10:44 AM Martin Liska wrote:
> >>
> >> Hi.
> >>
> >> It's becoming more common that a training run happens in parallel
> >> environment.
> >> That can lead to a not reprodu
On 6/5/19 3:49 PM, Richard Biener wrote:
> On Tue, Jun 4, 2019 at 10:44 AM Martin Liska wrote:
>>
>> Hi.
>>
>> It's becoming more common that a training run happens in parallel
>> environment.
>> That can lead to a not reproducible builds caused by different order of
>> merging
>> of .gcda files
On Tue, Jun 4, 2019 at 10:44 AM Martin Liska wrote:
>
> Hi.
>
> It's becoming more common that a training run happens in parallel environment.
> That can lead to a not reproducible builds caused by different order of
> merging
> of .gcda files. So that I'm suggesting to store up to 4 values for
Hi.
It's becoming more common that a training run happens in parallel environment.
That can lead to a not reproducible builds caused by different order of merging
of .gcda files. So that I'm suggesting to store up to 4 values for
HIST_TYPE_SINGLE_VALUE
and HIST_TYPE_INDIR_CALL on disk. If the cap
