performanceoptimization-wg July 2019

performanceoptimization-wg@lists.einsteintoolkit.org

3 participants
2 discussions

ET performance optimization call reminder
by rhaas＠illinois.edu 25 Jul '19

25 Jul '19

Hello all, just a reminder about this month's WG monthly call on Thursday, July 25 2019 at 11:00 AM CDT. The agenda is in the shared Google drive folder https://drive.google.com/drive/folders/1TEAYTb3pSE3NfQXAgvcCjKciRONQwuYU?us… and also linked on the wiki page https://docs.einsteintoolkit.org/et-docs/Working_Group_on_Performance_Optim… We will use this hangout for the call: https://hangouts.google.com/call/8XRtmArNv5CRm_DJpZUNAAEE Please make sure that you have finished all your TODO items before the call. Yours, Roland

4 4

SIMD Puzzle
by Zach Etienne 23 Jul '19

23 Jul '19

Hi all, I used NRPy+ to create a "minimal example" SIMD-intrinsics-enabled PDE solver kernel -- solving the scalar wave equation in 3 spatial dimensions. With AVX256+FMA intrinsics, neither Intel nor GNU compilers report success at fully vectorizing the RHS eval loop. E.g., the Intel compiler yields the cryptic message when compiling the innermost loop: remark #15310: loop was not vectorized: operation cannot be vectorized [ ScalarWave/ScalarWave_RHSs-SIMD.h(31,52) ] The line it's referring to has to do with loading data from memory _mm256_loadu_pd(&a). The entire source code is attached to this email, and I've been compiling using icc -restrict -align -qopenmp -xHost -O2 -qopt-report=5 -qopt-report-phase ipo -qopt-report-phase vec -vec-threshold1 -qopt-prefetch=4 ScalarWave_Playground-SIMD.c -o ScalarWave_Playground-SIMD for Intel 19, and for GNU (gcc 9): gcc -fsimd-cost-model=unlimited -Ofast -fopenmp -march=native ScalarWave_Playground-SIMD.c -fopt-info-vec-optimized-missed -o ScalarWave_Playground-SIMD -lm When I look at the Intel-generated annotated assembly of the innermost RHS loop (using icc -S -g -restrict -align -qopenmp -xHost -O2 -qopt-report=5 -qopt-report-phase ipo -qopt-report-phase vec -vec-threshold1 -qopt-prefetch=4 ScalarWave_Playground-SIMD.c), I see many 256-bit "ymmX"'s and corresponding instructions that seem to be consistent with the *math* intrinsics. I can't decipher much beyond that, though. Notably I didn't see any assembler instructions that look like _mm256_loadu_pd(). I fiddled around a bit with what goes inside the _mm256_loadu_pd(), just to see what might be causing the cryptic remark above. I found that if I remove dependence on the innermost loop variable "i0" on certain (obviously this would break the functionality, but the compiler doesn't care), then it is capable of vectorizing that loop. Note that the version of the code that does not use intrinsics is about 1.8x slower with either compiler, so I think intrinsics are providing some good benefit. However, I am discouraged by the compiler telling me that the inner loop cannot be fully vectorized. Any tips would be greatly appreciated! -Zach * * * Prof. Zachariah Etienne West Virginia University *https://math.wvu.edu/~zetienne/ <https://math.wvu.edu/~zetienne/>* https://blackholesathome.net

3 6

2026

2025

2024

2023

2022

2021

2020

2019

2018

performanceoptimization-wg July 2019