VectorAPI Testing Infrastructure custom loop trip count
Paul Sandoz
paul.sandoz at oracle.com
Mon Apr 2 18:37:17 UTC 2018
> On Apr 2, 2018, at 8:13 AM, Halimi, Jean-Philippe <jean-philippe.halimi at intel.com> wrote:
>
> Dear all,
>
> The following link is a patch adding support for a custom trip count for each test in the testing infrastructure.
>
> http://cr.openjdk.java.net/~jphalimi/webrev_testing_trip_count_v1.0/webrev/
>
> Please take a look and let me know your thoughts.
>
Do you have any views on whether the outer loop should cover just the kernel loop, or also include the allocation and assertion as in your patch?
I am unsure, but my suspicion it may be more more beneficial if it covers just the kernel loop so C2 is focused on the kernel, then allocation/assert code has less influence on the code shape.
Assuming the operations are deterministic, my suspicion is we are more interested in the correctness of a C2 produced code and less so on the intermediate results, which i think we can get coverage on with intrinsics off and/or with tiered compilation/C1 only.
Maybe later we configure what is in and outside the loop?
Paul.
More information about the panama-dev
mailing list