Skip to content

testing: hwy testing strategies#5136

Open
lgritz wants to merge 1 commit intoAcademySoftwareFoundation:mainfrom
lgritz:lg-hwy-test
Open

testing: hwy testing strategies#5136
lgritz wants to merge 1 commit intoAcademySoftwareFoundation:mainfrom
lgritz:lg-hwy-test

Conversation

@lgritz
Copy link
Copy Markdown
Collaborator

@lgritz lgritz commented Apr 10, 2026

  1. Some tests are repeated, run once with hwy off and once with hwy on. The "on" versions append ".hwy" to the test name and set the OPENIMAGEIO_ENABLE_HWY=1 environment variable to force it on while running the test. The advantage to this approach is that the test itself doesn't need to change at all, we just run it separately in each mode.

    In this PR, I do this with oiiotool, oiiotool-xform, and docs-examples-cpp.

    For now, while hwy is not enabled by default, it's doing these extra things to enable hwy. Eventually, if/when hwy is enabled by default, we'll flip the sense and use the env variable to turn it off.

  2. Some tests do certain operations both ways when hwy support was enabled at build time. This is more convenient for certain unit test executables, where perhaps we want to benchmark both ways and have those show up right next to each other within the run.

    In this PR, I do this with the imagebufalgo_test unit test.

1. Some tests are repeated, run once with hwy off and once with hwy
   on.  The "on" version append ".hwy" to the test name and set the
   OPENIMAGEIO_ENABLE_HWY=1 environment variable to force it on while
   running the test. The advantage to this approach is that the test
   itself doesn't need to change at all, we just run it separately in
   each mode.

   In this PR, I do this with oiiotool, oiiotool-xform, and
   docs-examples-cpp.

   For now, while hwy is not enabled by default, it's doing these
   extra things to enable hwy. Eventually, if/when hwy is enabled by
   default, we'll flip the sense and use the env variable to turn it
   off.

2. Some tests do certain operations both ways when hwy support was
   enabled at build time. This is more convenient for certain unit
   test executables, where perhaps we want to benchmark both ways
   and have those show up right next to each other within the run.

   In this PR, I do this with the imagebufalgo_test unit test.

Signed-off-by: Larry Gritz <lg@larrygritz.com>
@lgritz lgritz added internals Internal changes, not public APIs performance image processing Related to ImageBufAlgo or other image processing topic. labels Apr 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

image processing Related to ImageBufAlgo or other image processing topic. internals Internal changes, not public APIs performance

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant