Displaying 3 results from an estimated 3 matches for "print_el".
Did you mean:
print_l
2016 Oct 12
2
[test-suite] making polybench/symm succeed with "-Ofast" and "-ffp-contract=on"
...g all the results up. This will generate more
inaccuracies than comparing each value, and if that's too large an
error, then you reduce the number of samples.
For example, on cholesky, we sampled every 16th item of the array:
for (i = 0; i < n; i++) {
for (j = 0; j < n; j++)
print_element(A[i][j], j*16, printmat);
fputs(printmat, stderr);
}
using "print_element" because calling printf sucks.
These modifications are ok, because they don't change the tests nor
hides them from compiler changes.
cheers,
--renato
2016 Oct 12
4
[test-suite] making polybench/symm succeed with "-Ofast" and "-ffp-contract=on"
On Tue, Oct 11, 2016 at 10:39 PM, Sebastian Pop <sebpop.llvm at gmail.com> wrote:
> On Tue, Oct 11, 2016 at 10:20 PM, Hal Finkel <hfinkel at anl.gov> wrote:
>> ----- Original Message -----
>>> From: "Renato Golin" <renato.golin at linaro.org>
>>> To: "Sebastian Pop" <sebpop.llvm at gmail.com>
>>> Cc: "Hal
2016 Oct 12
8
[test-suite] making polybench/symm succeed with "-Ofast" and "-ffp-contract=on"
On 12 October 2016 at 14:26, Sebastian Pop <sebpop.llvm at gmail.com> wrote:
> Correct me if I misunderstood: you would be ok changing the
> reference output to exactly match the output of "-O0 -ffp-contract=off".
No, that's not at all what I said.
Matching identical outputs to FP tests makes no sense because there's
*always* an error bar.
The output of O0, O1, O2,