Class Layout Copyright © 2020 by Stephen C. Dewhurst and Daniel Saks 1 Class Layout Steve Dewhurst Semantics Consulting, Inc. www.stevedewhurst.com 1 Copyright © 2020 by Stephen C. Dewhurst and Daniel *emps[max]; size_t size; }; 7 Copyright © 2020 by Stephen C. Dewhurst and Daniel Saks 1 7Class Layout Copyright © 2020 by Stephen C. Dewhurst and Daniel Saks 2 sizeof(Class Object)  sizeof applied by Stephen C. Dewhurst and Daniel Saks Class Members That Don’t Affect Layout  Static data members do not affect class layout.  They have static lifetime or thread storage duration.  Therefore, we

ranks physically equal to multiple separate groups of memory components assembled on the same PCB • MDP and vendor marketing names for multilayer componentsMemory • What about HBM? Not 1024 bits requirements • Scalar, various vectors, specialty instructions, on-core and off- core accelerators • Data layout: both software and hardware characteristics 84 src dst • Alignment: source and destination mandatory. Control flow dependencies need to be translated to data flow dependencies. Data structure layout should not conflict with native vector width and length. • Controllable/maskable access to memory

view type without memory restrictions like the custom example, the view is a logical, not physical layout of the data reshaping doesn’t require any reallocation mdspans are typically very cheap customization p[i]; }github.com/griswaldbrooks/spanny2 layout policy 23github.com/griswaldbrooks/spanny2 layout policy maps multidimensional index to a storage location layout(N,M,Q,R,…) → offset 24github.com/griswaldbrooks/spanny2 com/griswaldbrooks/spanny2 standard layout policies 25github.com/griswaldbrooks/spanny2 layout_right = layout_leftT row major C++ arrays, numpy default layout layout_right(i, j): return i*M + j

size_t numRows_x, size_t numCols_x, class Layout_x, class Accessor_x, class ElementType_y, class SizeType_y, size_t numRows_y, size_t numCols_y, class Layout_y, class Accessor_y, class ElementType_z size_t numCols_z, class Layout_z, class Accessor_z> void add_rank_2( std::experimental::mdspan, Layout_x, Accessor_x> x, Type_y, numRows_y, numCols_y>, Layout_y, Accessor_y> y, std::experimental::mdspan, Layout_z, Accessor_z> z) { static_assert(x

Conan settings and options. 4.1. Consuming packages 33 Conan Documentation, Release 2.0.17 Use the layout() method In the previous examples, every time we executed a conan install command, we had to use type of CMake generator we are using. You can define this directly in the conanfile.py inside the layout() method and make it work for every platform without adding more changes. Listing 30: conanfile self.requires("zlib/1.2.11") def build_requirements(self): self.tool_requires("cmake/3.22.6") def layout(self): # We make the assumption that if the compiler is msvc the # CMake generator is multi-config

structure we want to follow and also to add some logic using Conan settings and options. Use the layout() method In the previous examples, every time we executed a conan install command, we had to use type of CMake generator we are using. You can define this directly in the conanfile.py inside the layout() method and make it work for every platform without adding more changes. Listing 31: conanfile build_requirements(self): if self.settings.os != "Windows": self.tool_requires("cmake/3.22.6") def layout(self): # We make the assumption that if the compiler is msvc the # CMake generator is multi-config

structure we want to follow and also to add some logic using Conan settings and options. Use the layout() method In the previous examples, every time we executed a conan install command, we had to use type of CMake generator we are using. You can define this directly in the conanfile.py inside the layout() method and make it work for every platform without adding more changes. Listing 31: conanfile build_requirements(self): if self.settings.os != "Windows": self.tool_requires("cmake/3.22.6") def layout(self): # We make the assumption that if the compiler is msvc the # CMake generator is multi-config

structure we want to follow and also to add some logic using Conan settings and options. Use the layout() method In the previous examples, every time we executed a conan install command, we had to use type of CMake generator we are using. You can define this directly in the conanfile.py inside the layout() method and make it work for every platform without adding more changes. Listing 31: conanfile build_requirements(self): if self.settings.os != "Windows": self.tool_requires("cmake/3.22.6") def layout(self): # We make the assumption that if the compiler is msvc the # CMake generator is multi-config

structure we want to follow and also to add some logic using Conan settings and options. Use the layout() method In the previous examples, every time we executed a conan install command, we had to use type of CMake generator we are using. You can define this directly in the conanfile.py inside the layout() method and make it work for every platform without adding more changes. Listing 31: conanfile build_requirements(self): if self.settings.os != "Windows": self.tool_requires("cmake/3.22.6") def layout(self): # We make the assumption that if the compiler is msvc the # CMake generator is multi-config

structure we want to follow and also to add some logic using Conan settings and options. Use the layout() method In the previous examples, every time we executed a conan install command, we had to use type of CMake generator we are using. You can define this directly in the conanfile.py inside the layout() method and make it work for every platform without adding more changes. Listing 31: conanfile build_requirements(self): if self.settings.os != "Windows": self.tool_requires("cmake/3.22.6") def layout(self): # We make the assumption that if the compiler is msvc the # CMake generator is multi-config